data transmission method, device, access network device, terminal, computer program product and comm

专利摘要:
this application provides a method of data transmission. a first access network device establishes a first drb (radio data carrier) and a second drb; the first access network device receives data packets forwarded from a second access network device, the first access network device maps, to the first rdb, a data packet in the forwarded data packets that does not include a flow identifier , wherein the first drb corresponds to a dbr of the second access network device; and the first access network device maps, to the second drb based on a second mapping relationship, a data packet in the forwarded data packets that includes a flow identifier, where the second mapping relationship is a mapping between a stream and a drb on the first access network device. however, the following problem is avoided: in an automatic switch or dual connectivity or other scenario, a data packet is lost or repeatedly transmitted because each access network device independently sets up a mapping relationship between a stream and a drb. this improves continuity of terminal service and improves communication quality.
公开号:BR112019019834A2
申请号:R112019019834
申请日:2018-03-24
公开日:2020-04-22
发明作者:Han Lifeng；Dai Mingzeng；Huang Qufang
申请人:Huawei Tech Co Ltd；
IPC主号:

专利说明:

“DATA TRANSMISSION METHOD, APPLIANCE, ACCESS NETWORK DEVICE, TERMINAL, COMPUTER PROGRAM PRODUCT AND COMMUNICATION SYSTEM”
TECHNICAL FIELD [0001] This request refers to the field of wireless communication and, in particular, to a method of data transmission, an access network device, a terminal and a communications system.
FUNDAMENTALS [0002] With the continuous increase in user requirements, more in-depth research is done on a new radio access network (New RAN). The new radio access network can provide less delay and greater bandwidth and support more connections than an existing wireless communication system to meet growing mobile communication requirements.
[0003] In the new radio access network, the management of quality of service (quality of service, QoS) is based on a flow (flow) and includes: establishing a session of protocol data unit (protocol data unit, PDU ) between an access network device and a main network, where the PDU session can include a plurality of flows and different flows may have different QoS requirements; provide a flow-through QoS requirement to the base station over the main network; and complete, from the base station, the mapping from the stream to a data radio bearer (data radio bearer, DRB) based on the QoS requirements. For example, the base station maps flows having the same QoS requirement to the same DRB and transmit the flows in the DRB.
[0004] During data transmission between base stations, for example, in a scenario of automatic switching (handover) or dual connectivity (dual connection, DC), a tunnel is established between a source base station and a station destination base packet, a terminal data packet at the source base station is sent to the destination base station, and then the destination base station communicates with a terminal. Because the destination base station and the source base station can set up different mapping relationships between a stream and a DRB, the terminal data packet can be lost or transmitted
Petition 870190103851, of 10/15/2019, p. 7/96
2/75 quickly or similar to being sent to the destination base station or subsequently being transmitted via an air interface. As a result, the communication continuity of the terminal is affected.
SUMMARY [0005] The modalities of this application provide a data transmission method, an access network device, a terminal and a communication system.
[0006] According to a first aspect, an embodiment of this request provides a method of data transmission, including:
receiving, by means of a first access network device, data packets forwarded from a second access network device; map, by the first network device to access a first data radio bearer (data radio bearer, DRB), a data packet in the forwarded data packets that does not include a flow identifier, where the first DRB corresponds to a DRB of the second access network device; and map, by the first network device to access a second DRB based on a second mapping relation, a data packet in the forwarded data packets that includes a flow identifier, where the second mapping relation is a mapping relation between a stream and a DRB on the first access network device.
[0007] The first DRB and the DRB of the second access network device serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device. The first DRB is a DRB reflected from the DRB of the second access network device.
[0008] Forwarded data packets include at least one type of the following data packets: a packet data convergence protocol (PDCP) layer data packet that is from the second access network device , to which a sequence number is allocated, and for which confirmation of receipt is not obtained from a terminal; a PDCP layer data packet that is from the second access network device and for which no sequence number is allocated; and a service data adaptation protocol (SDAP) layer data package from the
Petition 870190103851, of 10/15/2019, p. 8/96
3/75 second access network device.
[0009] On the premise that each access network device can independently define a mapping relationship between a stream and a DRB, the data packet that has a stream identifier is mapped to the second DRB for transmission and the packet of data data that does not have the stream identifier is mapped to the first DRB for transmission. Therefore, a way of transmitting a data packet can be selected based on a real state of the network, to avoid the following problem: In an automatic change or dual connectivity or other scenario, a data packet is lost or is transmitted repeatedly by the the fact that each access network device independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0010] In a possible implementation, the first access network device sends, to the terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier and to which a sequence number is allocated; and the first access network device sends, to the terminal in the second DRB, a data packet in the forwarded data packets that includes a flow identifier and for which no sequence number is allocated. The data packet can be a PDCP layer data packet, and therefore the sequence number is a PDCP layer sequence number.
[0011] In a possible implementation, the first access network device sends, to the terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier; and the first access network device sends, to the terminal in the second DRB, a data packet in the forwarded data packets that includes a flow identifier. The data packet that includes a stream identifier can be a PDCP layer data packet to which a stream identifier is allocated and / or an SDAP layer data packet.
[0012] In a possible implementation, the method additionally includes: routing, through the first network device of access to the second DRB through an SDAP entity, the data packet in the forwarded data packets that includes a flow identifier.
Petition 870190103851, of 10/15/2019, p. 9/96
4/75 [0013] In a possible implementation, receiving, through a first access network device, data packets forwarded from a second access network device includes: receiving, through the first network device access, data packets forwarded from the second access network device through a tunnel established on the basis of a DRB and a tunnel established on the basis of a session, where the tunnel established on the basis of a DRB is used to transmit a PDCP layer data packet that is from the second access network device and to which a sequence number is allocated; and the tunnel established on the basis of a session is used to transmit the SDAP layer data packet from the second access network device, and / or is used to transmit a PDCP layer data packet which is from the second access network device access, which includes a stream identifier and for which no sequence number is allocated.
[0014] In a possible implementation, the receipt, by means of a first access network device, of data packets forwarded from a second access network device includes: receiving, by the first access network device, data packets forwarded from the second access network device through a tunnel established on the basis of a DRB. There may be one or more tunnels established on the basis of a DRB. For example, when there are two tunnels established on the basis of a DRB, one tunnel can be used to transmit the data packet which has a flow identifier and the other tunnel can be used to transmit the data packet which does not have a flow identifier. flow.
[0015] In a possible implementation, the receipt, by means of a first access network device, of data packets forwarded from a second access network device includes: receiving, by the first access network device from of the second network device accessing through a tunnel established on the basis of a session, the data packet in the forwarded data packets that includes a flow identifier. Optionally, the first access network device routes, to the first DRB through the SDAP entity, a PDCP layer data packet that is received from the tunnel established on the basis of a session and for which a sequence number is allocated , and routes, for the second DRB, a
Petition 870190103851, of 10/15/2019, p. 10/96
5/75 PDCP layer data packet for which no sequence number is allocated or the SDAP layer data packet.
[0016] The previous ways of tunneling are applicable to a plurality of forwarded packet data transmission scenarios. A forwarded data packet that includes a stream identifier, a forwarded data packet that does not include a stream identifier, a forwarded data packet to which a sequence number is allocated and a forwarded data packet to which no number of sequence is allocated can all be transmitted through suitable tunnels. Therefore, one is prevented from losing packets or the repeated transmission of packets in a data forwarding process and network performance is improved.
[0017] In a possible implementation, after the sending of the forwarded data packet mapped to the first DRB is completed, the method additionally includes: releasing, by the first access network device, the first DRB, to save a system resource.
[0018] In a possible implementation, the first access network device can send the second mapping relation to the second access network device and send the second mapping relation to the terminal through the second access network device.
[0019] According to a second aspect, one embodiment of this request provides a method of data transmission, including: receiving, by means of a first access network device, data packets forwarded from a second network device access; and map, by the first network device accessing a first DRB, at least one data packet in the forwarded data packets that includes a flow identifier, where the first DRB corresponds to a DRB of the second access network device.
[0020] The first DRB and the DRB of the second access network device serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device.
[0021] Forwarded data packets include at least one type of the following data packets: a PDCP layer data packet that is from the second access network device, to which a sequence number
Petition 870190103851, of 10/15/2019, p. 11/96
6/75 is allocated, and to which no acknowledgment of receipt is obtained from a terminal; a PDCP layer data packet that is from the second access network device and for which no sequence number is allocated; and an SDAP layer data packet from the second access network device.
[0022] In a possible implementation, the method additionally includes: mapping, by the first network device accessing the first DRB, a data packet in the forwarded data packets that does not include a flow identifier.
[0023] In a possible implementation, the method additionally includes: mapping, by the first network device accessing a second DRB based on a second mapping relationship, at least one data packet in the forwarded data packets that includes an identifier flow and which is different from the data packet mapped to the first DRB, where the second mapping relationship is a mapping relationship between a flow and a DRB on the first access network device.
[0024] In a possible implementation, the first access network device sends the data packets forwarded to the terminal in the first DRB or in the first DRB and in the second DRB.
[0025] Optionally, in the second aspect, different types of tunnels can be established between the first access network device and the second access network device to transmit the forwarded data packets. For an example of a specific type of tunnel, see the descriptions listed in the first aspect. The details are not described again. Several ways of establishing tunnels are applicable to a plurality of forwarded packet data transmission scenarios. A forwarded data packet that includes a stream identifier, a forwarded data packet that does not include a stream identifier, a forwarded data packet to which a sequence number is allocated and a forwarded data packet to which no number of sequence is allocated can all be transmitted through suitable tunnels. Therefore, packet loss or repeated packet transmission is avoided in a data forwarding process and network performance is improved.
[0026] In a possible implementation, the method includes
Petition 870190103851, of 10/15/2019, p. 12/96
7/75 additionally: send, by the first network device of access to the terminal in the first DRB, a PDCP layer data packet that is in the forwarded data packets and to which a sequence number is allocated; and sending, by the first terminal access network device in the second DRB, a PDCP layer data packet that is in the forwarded data packets and to which no sequence number is allocated.
[0027] In a possible implementation, after the sending of the forwarded data packets mapped to the first DRB is completed, the method additionally includes: releasing, by the first access network device, the first DRB.
[0028] In a possible implementation, the first access network device can send the second mapping relation to the second access network device and send the second mapping relation to the terminal through the second access network device.
[0029] According to the method of data transmission provided in this modality of this request, the first access network device sends the data packets forwarded to the terminal in the first DRB corresponding to the second access network device. In addition, for better network performance, the first access network device establishes the second DRB. The second DRB is used to transmit the data packet in the forwarded data packets that have a stream identifier and that is different from the data packet mapped to the first DRB, and the second DRB meets the mapping relationship that is between a stream and a DRB and that is configured by the first access network device. Therefore, forwarded data packets can be transmitted in a variety of flexible transmission ways on different DRBs, and a data packet transmission way can be selected based on a real state of the network, to avoid the problem: In an automatic changeover or dual connectivity or another scenario, a data packet is lost or is transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0030] According to a third aspect, a modality of this request provides a method of data transmission, including: generating, through
Petition 870190103851, of 10/15/2019, p. 13/96
8/75 of a first access network device, a forwarded data packet that includes a flow identifier; and sending, by the first access network device to a second access network device, the forwarded data packet that includes a flow identifier.
[0031] In a possible implementation, the method additionally includes: sending, by the first access network device, a first mapping relation to the second access network device, where the first mapping relation is a mapping relation between a stream and a DRB on the second access network device.
[0032] In a possible implementation, the generation, through a first access network device, of a forwarded data packet that includes a flow identifier includes:
obtain, by the first access network device, a cache location of the forwarded data packet, where the cache location corresponds to the flow identifier of the forwarded data packet; obtain, by the first access network device, the flow identifier of the forwarded data packet based on the cache location; and adding, by the first access network device, the flow identifier to a header of the forwarded data packet.
[0033] In a possible implementation, the method additionally includes: sending, by the first access network device to the second access network device, a forwarded data packet that does not include a flow identifier.
[0034] In a possible implementation, forwarded data packets include at least one type of the following data packets: a PDCP layer data packet that is from the first access network device, to which a sequence number is allocated, and for which there is no acknowledgment of receipt it is obtained from a terminal; a PDCP layer data packet that is from the first access network device and for which no sequence number is allocated; and an SDAP layer data packet from the first access network device.
[0035] In a possible implementation, the forwarded data packet includes an out-of-service data packet received by the first access network device from the terminal.
Petition 870190103851, of 10/15/2019, p. 14/96
9/75 [0036] According to a fourth aspect, one embodiment of this request provides a method of data transmission, including: receiving, by means of a first access network device, a data packet forwarded from a second access network device, where the forwarded data packet includes a flow identifier, and the forwarded data packet includes an out-of-service PDCP layer data packet received by the second access network device from a terminal.
[0037] In a possible implementation, the receipt, by means of a first access network device, of a data packet forwarded from a second access network device includes: receiving, by the first access network device, the data packet forwarded from the second access network device through a tunnel established on the basis of a DRB.
[0038] In a possible implementation, the method additionally includes: receiving, by the first access network device, uplink data packets from the terminal, where uplink data packets include at least one type of the following packets data: a PDCP layer data packet that is unsuccessfully sent by the terminal to the second access network device and to which a sequence number is allocated; a PDCP layer data packet that is from the terminal and for which no sequence number is allocated; and an SDAP layer data packet from the terminal.
[0039] In a possible implementation, the reception, by the first access network device, of uplink data packets from the terminal includes: receiving, by the first access network device, the uplink data packets in the first DRB; or receiving, by the first access network device, the uplink data packets in the second DRB.
[0040] In a possible implementation, the receipt, by the first access network device, of uplink data packets from the terminal includes: receiving, by the first access network device in the first DRB, a data packet from PDCP layer that is from the terminal and for which a sequence number is allocated in the uplink data packets; and receive, by the first access network device on the second
Petition 870190103851, of 10/15/2019, p. 15/96
10/75
DRB, the PDCP layer data packet that is from the terminal and for which no sequence number is allocated in the uplink data packets and / or the SDAP Service Data Adaptation Protocol layer data packet from the terminal uplink data packets.
[0041] In a possible implementation, the reception, by the first access network device, of uplink data packets from the terminal includes: receiving, by the first access network device, a PDCP layer data packet from the terminal. terminal on the uplink data packets in the first DRB; and receiving, by the first access network device, the SDAP Service Data Adaptation Protocol layer data packet from the terminal in the uplink data packets in the second DRB.
[0042] According to the method of data transmission provided in this modality of this request, in an uplink direction, the first access network device receives, from the second access network device, the forwarded data packet that includes a flow identifier. The forwarded data packet includes the out-of-service data packet received by the second access network device from the terminal. After the forwarding of the forwarded data packet is complete, the terminal can send the uplink data packets to one side of the network in various flexible transmission ways on different DRBs, and a data packet transmission way can be selected with based on a real state of the network, to avoid the problem: In an automatic switch or dual connectivity or other scenario, a data packet is lost or is transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a flow and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0043] According to a fifth aspect, one embodiment of this request provides a method of data transmission, including: sending, through a terminal, uplink data packets to a first access network device, where the packets uplink data includes flow identifiers; and / or receive data packets from the terminal
Petition 870190103851, of 10/15/2019, p. 16/96
11/75 downlink from the access network device, where at least one of the downlink data packets includes a flow identifier, and the downlink data packets include a forwarded data packet sent via a second access network device for the first access network device.
[0044] In a possible implementation, the sending, through a terminal, of uplink data packets to an access network device includes: sending, through the terminal to the first access network device in a first DRB, a PDCP layer data packet that is in the uplink data packets and to which a sequence number is allocated; and sending, through the terminal to the first access network device in a second DRB, a PDCP layer data packet for which no sequence number is allocated in the uplink data packets and / or a layer data packet SDAP in uplink data packets, where the first DRB serves a mapping relationship between a flow and a DRB on the second access network device, and the second DRB serves a mapping relationship between a flow and a DRB on the first device access network.
[0045] In a possible implementation, sending, through a terminal, uplink data packets to an access network device includes: sending, through the terminal, a PDCP layer data packet in the data packets of uplink to the access network device in a first DRB; and sending, through the terminal, an SDAP layer data packet in the uplink data packets to the access network device in a second DRB.
[0046] In a possible implementation, the reception, by the terminal, of downlink data packets from the access network device includes: receiving, by the terminal from the first access network device in the first DRB, a packet of data in the downlink data packets that does not include a flow identifier; and receiving, by the terminal from the first access network device in the second DRB, a data packet in the downlink data packets that includes a flow identifier.
[0047] In a possible implementation, the receipt, by the
Petition 870190103851, of 10/15/2019, p. 17/96
12/75 terminal, of downlink data packets from the access network device includes: receiving, by the terminal from the first access network device in the first DRB, a PDCP layer data packet that is in the packets downlink data and for which a sequence number is allocated; and receiving, from the first access network device in the second DRB, a PDCP layer data packet that includes a flow identifier and for which no sequence number is allocated in the downlink data packets and / or a SDAP layer data packet in downlink data packets.
[0048] In either implementation of the fifth aspect, the first DRB meets the mapping relationship between a flow and a DRB on the second access network device, and the second DRB meets the mapping relationship between a flow and a DRB on the first access network device.
[0049] According to a sixth aspect, one embodiment of this request provides an access network device. The access network device has a function of implementing the behavior of the first access network device in any of the previous data transmission methods, or it has a function of implementing the behavior of the second access network device in any of the previous data transmission methods. The function can be implemented by hardware, or it can be implemented by hardware by running the corresponding software. The hardware or software includes one or more units or means (means) corresponding to the function.
[0050] In a possible implementation of the sixth aspect, an access network device structure includes a processor and a transceiver. The processor is configured to support the access network device that performs the corresponding function in the previous data transmission methods. The transceiver is configured to: support communication between the access network device and a terminal, and send information or instructions on previous data transmission methods to the terminal. The access network device may additionally include a memory. The memory is configured to be coupled to the processor, and the memory stores the necessary program instructions and the necessary data from the
Petition 870190103851, of 10/15/2019, p. 18/96
13/75 access network device. The access network device may additionally include a communication interface. The communication interface is configured to communicate with another network device.
[0051] In a possible implementation, the access network device is a base station.
[0052] According to a seventh aspect, an embodiment of this request provides a terminal. The terminal has a function of implementing the behavior of the terminal in any of the previous data transmission methods. The function can be implemented by hardware, or it can be implemented by hardware by running the corresponding software. The hardware or software includes one or more units or means (means) corresponding to the function.
[0053] In a possible implementation of the seventh aspect, a terminal structure includes a processor and a transceiver. The processor is configured to support the terminal that performs the corresponding function in the previous data transmission methods. The transceiver is configured to: support communication between an access network device and the terminal, and send information or instructions on previous data transmission methods to the access network device. The terminal can additionally include a memory. The memory is configured to be coupled to the processor, and the memory stores the necessary program instructions and the necessary data from the terminal.
[0054] According to an eighth aspect, an embodiment of the present invention provides a communication system, including the access network device and the terminal in the foregoing aspects.
[0055] According to a ninth aspect, one embodiment of this request provides a computer-readable storage medium. Computer-readable storage media stores instructions. When the computer-readable storage media is carried on a computer, the computer performs the method of transmitting data in any of the above aspects.
[0056] According to a tenth aspect, one embodiment of this application provides a computer program product that includes instructions. When the computer program product is driven on a computer,
Petition 870190103851, of 10/15/2019, p. 19/96
14/75 the computer performs the method of data transmission in any of the previous aspects.
[0057] According to a tenth aspect, an embodiment of this application provides an apparatus, comprising at least one processor coupled with at least one memory, wherein the at least one processor is configured to execute instructions stored in at least one memory to deploy the method according to any of the previous aspects, for example from the first aspect to the fifth aspect.
[0058] According to a tenth aspect, one embodiment of this request provides an apparatus, the apparatus is configured to carry out the method in accordance with any of the previous aspects, for example from the first aspect to the fifth aspect.
[0059] According to the technical solutions provided in these modalities of this application, several ways of transmitting flexible forwarded data packets are used to avoid the problem: In an automatic change or dual connectivity or other scenario, a data packet is lost or it is transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
BRIEF DESCRIPTION OF THE DRAWINGS [0060] To describe the technical solutions in these modalities of this application more clearly, the following are briefly described the attached drawings necessary to describe the modalities. Apparently, the attached drawings in the following descriptions show merely some of the modalities of this application, and a professional with ordinary skill in the art can still derive other designs from these attached drawings without creative efforts.
[0061] FIG. 1 is a schematic diagram of a communication system, according to an embodiment of this request;
[0062] FIG. 2 is a schematic flowchart of a data transmission method, according to an embodiment of this request;
[0063] FIG. 3 is a schematic flow chart of a data transmission method, according to an embodiment of this request;
Petition 870190103851, of 10/15/2019, p. 20/96
15/75 [0064] FIG. 4 is a schematic flow chart of a data transmission method, according to an embodiment of this request;
[0065] FIG. 5 is a schematic flowchart of a data transmission method, according to an embodiment of this request;
[0066] FIG. 6 is a schematic signaling flowchart for a data transmission method, according to one embodiment of this request;
[0067] FIG. 7 is a structural schematic diagram of an access network device 700, according to an embodiment of this application;
[0068] FIG. 8 is a structural schematic diagram of an access network device 800, according to an embodiment of this application;
[0069] FIG. 9 is a structural schematic diagram of an access network device 900, according to an embodiment of this application;
[0070] FIG. 10 is a structural schematic diagram of an access network device 1000, according to an embodiment of this application;
[0071] FIG. 11 is a structural schematic diagram of a terminal 1100, according to an embodiment of this application;
[0072] FIG. 12 is a structural schematic diagram of an access network device 1200, according to an embodiment of this application;
[0073] FIG. 13 is a structural schematic diagram of an access network device 1300, according to an embodiment of this application;
[0074] FIG. 14 is a structural schematic diagram of a terminal 1400, according to an embodiment of this application; and [0075] FIG. 15 is a schematic diagram of a communication system 1500, according to an embodiment of this request.
DESCRIPTION OF THE MODALITIES [0076] The technologies described in the modalities of this application can be used in a 5G communication system (the fifth generation, fifth generation), or another communication system of the next generation, for example, a new radio access network (New RAN, NR).
[0077] The access network device described in these modalities of this application includes a base station device in NR, for example, a
Petition 870190103851, of 10/15/2019, p. 21/96
16/75 gNB, a transmission point (transmission point, TRP), or a base station device including a central unit (central unit, CU) and a distributed unit (distributed unit, DU). CU can also be referred to as a control unit. When a base station device, that is, an evolved Node B, evolved nodeB, eNB, in a long term evolution (LTE) system can be connected to a main 5G network (5G Core Network, 5G CN), LTE eNB can also be referred to as an eLTE eNB. Specifically, the eLTE eNB is an LTE base station device evolved from LTE eNB, and can be connected directly to the CN 5G. The eLTE eNB is also a NR base station device. Alternatively, the access network device can be an access point (access point, AP), or another network device capable of communicating with a terminal and a main network. One type of access network device is not particularly limited in these embodiments of this application.
[0078] The CN 5G described in these modalities of this application can also be referred to as a new main network (new core), a new main network 5G, a new main network of the next generation (next generation core, NGC) or similar. The CN 5G is arranged independently of an existing main network such as an evolved packet core, EPC.
[0079] The terminal in these modalities of this application may include a portable device, a device in the vehicle, a wearable device, or a computing device that has a wireless communication function, another processing device connected to a wireless modem, or user equipment (user equipment, UE), a mobile station (mobile station, MS), a terminal device (terminal equipment), or the like that are in various forms.
[0080] In these modalities of this request, a unidirectional communication link from an access network to the terminal is defined as a downlink, the data transmitted on the downlink is downlink data, and a direction of transmission of data from downlink is referred to as a downlink direction; and a unidirectional communication link from the terminal to the access network is an uplink, the data transmitted on the uplink is data from
Petition 870190103851, of 10/15/2019, p. 22/96
17/75 uplink, and an uplink data transmission direction is referred to as an uplink direction.
[0081] An original access network device described in these modalities of this application is an access network device that the terminal currently accesses or encapsulates, and the terminal must be changed automatically from the access network device to another access device. access network. Correspondingly, a target access network device described in these embodiments of this application is an access network device to which the terminal must be changed automatically.
[0082] It should be understood that the term “and / or” in this specification describes only one association relationship between associated objects and indicates that three relationships can exist. For example, A and / or B can indicate the following three cases: Only A exists, both A and B exist and only B exists. In addition, the “/” character in this specification indicates an “or” relationship between associated objects.
[0083] In these modalities of this request, "a plurality of" refers to "two or more".
[0084] Descriptions such as "first" and "second" in these modalities of this application are merely used to illustrate and distinguish between the objects described, and are not indented to indicate a sequence or indicate a special limitation on a number of devices in these modalities this order. These descriptions must not constitute any limitation in these modalities of this application.
[0085] In these modalities of this application, "connection" means several ways of connection such as a direct connection or an indirect connection, to implement the communication between the devices. This is not limited to these modalities of this application.
[0086] In these modalities of this request, "network" and "system" express the same concept, and a communication system is a communication network.
[0087] FIG. 1 is a schematic diagram of a communication system, according to an embodiment of this request.
[0088] As shown in FIG. 1, the communication system includes a main network device 110, a first access network device
Petition 870190103851, of 10/15/2019, p. 23/96
18/75
120, a second access network device 130 and a terminal 140. The first access network device 120 and the second access network device 130 communicate separately with the main network device 110 via the communication interfaces. For example, the communication interface is an NG interface shown in FIG. 1. It can be a communication interface between the first access network device 120 and the second access network device 130, for example, an interface Xn shown in FIG. 1, configured to exchange information between devices.
[0089] It can be understood that the main network device 110 is a main network device in a CN 5G, and includes one or more functional entities arranged or integrated independently. For example, the main network device 110 may include a control plane network element (control plane, CP) and a user plane network element (user plane, UP) such as a user plan gateway (user plane gateway, UPGW).
[0090] Optionally, the first access network device 120 or the second access network device 130 is a gNB or an eLTE eNB. This is not limited in this mode of this application. For example, the first access network device 120 is a gNB and the second access network device 130 is a gNB; or the first access network device 120 is an eLTE eNB and the second access network device 130 is an eLTE eNB; or the first access network device 120 is a gNB and the second access network device 130 is an eLTE eNB; or the first access network device 120 is an eLTE eNB and the second access network device 130 is a gNB.
[0091] The main network device 110 communicates separately with the first access network device 120 and / or with the second access network device 130 through a protocol data unit session (protocol data unit, PDU ) (session). A PDU session can include a plurality of flows. Different flows may have the same QoS requirement or different QoS requirements. The main network device 110 provides a flow QoS requirement for the first access network device 120 and / or the second access network device 130, and the first access network device 120 and / or the second access network device 130 complete / complete the mapping from the stream to a DRB.
Petition 870190103851, of 10/15/2019, p. 24/96
19/75
Correspondingly, the flows included in a DRB have the same QoS or similar requirement. Specifically, the access network device can establish at least one DRB for each session of a terminal that accesses the access network device, including a standard DRB (default DRB). The DRB is established between the access network device and the terminal to transmit data from the air interface.
[0092] In this embodiment of this request, a flow that has a specific QoS requirement can be referred to as a QoS flow, and a QoS flow includes at least one data packet. Each QoS flow corresponds to one or more types of services. The QoS flow is briefly referred to as "flow" in the following modalities.
[0093] In a possible scenario of automatic changeover (handover), in a movement process, terminal 140 accesses an access network device through an automatic changeover, to obtain an ideal communication service. For example, when terminal 140 moves from a signal coverage area of the first access network device 120 currently accessed by terminal 140 to a signal coverage area of the second access network device 130, the terminal 140 can initiate an automatic switching procedure to switch automatically from the first access network device 120 to the second access network device 130. In the process of automatic switching, the first access network device 120 can send, to the second access network device 130, a stream that the first access network device 120 is ready to transmit to terminal 140. The second access network device 130 can map the stream that the first access network device 120 is ready to transmit to terminal 140 to a DRB that meets a flow QoS requirement and then transmit the flow to the terminal in the DRB.
[0094] In a possible scenario of dual connectivity (dualconnection, DC), terminal 140 accesses both the first access network device 120 and the second access network device 130. When the first access network device 120 determines to download some services for the second access network device 130, the first access network device 120 can send a stream corresponding to the services to the second access network device 130. The second access network device
Petition 870190103851, of 10/15/2019, p. 25/96
20/75 access 130 can map the stream to a DRB that meets a QoS requirement of the stream and then transmit the stream to the terminal on the DRB. Based on different functions, the access network devices connected to the terminal can be classified into a master access network device that has a control plan function and a user plan function that are related to the terminal, and a device secondary access network that can be configured to carry out data transmission from the user plan with the terminal. The master access network device can control a terminal service to be migrated between the master access network device and the secondary access network device, and there is no need to distinguish between the master access network device and the device secondary access network when a flow corresponding to the service is routed between the access network devices and transmitted over an air interface. Therefore, there is no need to limit the first access network device 120 and the second access network device 130 to master access network devices or secondary access network devices. It can be understood that the terminal can alternatively access a master access network device and a plurality of secondary access network devices. The details are not described.
[0095] In the process of automatic switching or a dual connectivity process, the first access network device 120 sends the data packets related to terminal 140 to the second access network device 130 and then the second access device access network 130 transmits the data packets to terminal 140. The data packets belong to one or more streams. The data packet transmission process can be referred to as data forwarding, or it can be referred to as reverse data transmission or data transmission.
[0096] Specifically, a tunnel can be established between the first access network device 120 and the second access network device 130 to transmit a data packet that needs data forwarding. The tunnel can be established based on a DRB, or it can be established based on an SDAP entity or session. Alternatively, the two types of tunnels can be established. In other words, one tunnel is established based on a DRB, and the other tunnel is
Petition 870190103851, of 10/15/2019, p. 26/96
21/75 established based on an SDAP entity or session. The tunnel established on the basis of a DRB can be used to transmit a PDCP layer data packet corresponding to the DRB. The tunnel established on the basis of a session or an SDAP entity can be used to transmit a cache data packet on an SDAP layer or transmit a PDCP layer data packet that carries a flow identifier. The SDAP layer is a user plane protocol layer established above a user plane PDCP layer in a protocol stack on one side of the access network connected to an NGC network. The SDAP layer can be used to map a stream from a non-access stratum, NAS to a DRB from an access stratum (access stratum, AS). The SDAP entity is an instance that is established at the SDAP layer to complete a function at the SDAP layer. The SDAP entity is also responsible for adding a flow identifier to an air interface protocol stack. The stream identifier includes an uplink stream identifier or a downlink stream identifier, used to identify an uplink data stream or a downlink data stream. An access network device can map different flows to the same DRB or different DRBs based on a flow identifier for each flow and a QoS requirement for each DRB, in other words, establish a mapping relationship between a flow and a DRB. For example, if a stream 1 transmitted over the main network to the access network device is a stream corresponding to a machine type communication service (MTC), and a stream 2 is a stream corresponding to a network service. mobile broadband (MBB), it is considered that the access network device supports different types of services, and flow 1 and flow 2 can be mapped to the same DRB as the access network device, for example , a standard DRB, or can be mapped to two DRBs.
[0097] It can be understood that the SDAP entity or the SDAP layer can be referred to with another name, for example, an entity or layer of the Packet Data Association Protocol (PDAP). Any protocol layer that conforms to the previous SDAP layer definition and function descriptions if
Petition 870190103851, of 10/15/2019, p. 27/96
22/75 falls within the scope of protection of the SDAP layer described in this modality of this application.
[0098] Because each access network device independently defines a mapping relationship between a flow and a DRB, after the previous data packet that needs data forwarding is sent to the second access network device 130, if the second access network device 130 still transmitting the data packet based on a mapping relationship that is between a stream and a DRB and which is configured by the first access network device 120, the data packet can be lost or transmitted repeatedly. This affects the continuity of the terminal service.
[0099] Therefore, the modalities of this request provide a method of data transmission, to solve the following problem about how to forward data and how to transmit, through an air interface, a data package that needs data forwarding, in a premise that each access network device independently defines a mapping relationship between a stream and a DRB, especially in a scenario of automatic switching or dual connectivity.
[0100] To facilitate the description, “first access network device” or “second access network device” has the same meaning in the following modalities. The details are not described below again. For example, in an automatic switching process, the first access network device in these embodiments of this application can be a destination access network device and the second access network device can be a source access network device. In a scenario of dual connectivity, the second access network device in these modalities of this request can offload some services to the first access network device, and the first access network device transmits the services to a terminal. For example, when a master cell group bearer, MCG bearer, is used, the second access network device is a master base station and the first access network device is a secondary base station. ; or when a secondary cell group bearer (SCG bearer) is used, ο second access network device is a secondary base station and the
Petition 870190103851, of 10/15/2019, p. 28/96
23/75 first access network device is a master base station.
[0101] FIG. 2 is a schematic flow chart of a data transmission method, according to an embodiment of this request.
[0102] The data transmission method provided in this application is applicable to several communication scenarios that have a data forwarding process between base stations, such as an automatic switching process or a dual terminal connectivity process. This is not limited in this mode of this application.
[0103] The method includes the following steps.
[0104] S201. A first access network device receives forwarded data packets (or a forwarded data packet) from a second access network device.
[0105] Forwarded data packets are data packets that need data forwarding and that are sent by the second access network device to the first access network device, that is, data packets sent by the second access network device. access to the first access network device in a data forwarding process.
[0106] Specifically, in a downlink direction, forwarded data packets include at least one type of the following data packets: a PDCP layer data packet from the second access network device, to which a sequence number ( sequence number, SN) is allocated, and for which confirmation of receipt is not obtained from a terminal; a PDCP layer data packet from the second access network device to which no sequence number is allocated; and an SDAP layer data packet from the second access network device.
[0107] PDCPs layer data packets include a PDCP PDU and a PDCP SDU. When the second access network device routes the PDCP PDU to the first access network device, the second access network device can perform processing such as decryption or protocol header removal on the PDCP PDU, to obtain a PDCP SDU to which a sequence number is retained. Therefore, all PDCP layer data packets are routed between base stations in a form of PDCP SDUs, including a PDCP SDU to which a number of
Petition 870190103851, of 10/15/2019, p. 29/96
24/75 sequence is allocated and a PDCP SDU for which no sequence number is allocated. In this embodiment of this request, the PDCP SDU sequence number is a PDCP layer sequence number that can be denoted as a PDCP SN.
[0108] S202. The first access network device maps, to a first DRB, at least one data packet in the forwarded data packets that includes a flow identifier, where the first DRB corresponds to a DRB of the second access network device.
[0109] The first access network device can map, to the first DRB, all data packets including flow identifiers in forwarded data packets or some data packets including flow identifiers in forwarded data packets.
[0110] The first DRB and the DRB of the second access network device serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device. Specifically, the first DRB is established by the first access network device and is used to transmit data between the first access network device and the terminal. When the first access network device receives information about one or more DRB streams from the second access network device, the first access network device can establish a reflected DRB. The reflected DRB can maintain a transmission state of a specific DRB from the second access network device, to continue transmitting a data packet in the DRB of the second access network device. To facilitate description, a DRB of the second access network device corresponding to the reflected DRB can be referred to as a “third DRB”. Specifically, the reflected DRB has the same PDCP SN state and the hyper frame number (HFN) as the third DRB. The PDCP SN state and the HFN state can indicate a sending state and a receiving state of a PDCP data packet in the DRB. The reflected DRB is the previous “first DRB”.
[0111] Optionally, the first access network device receives the first mapping relation from the second access network device.
[0112] Optionally, the first access network device
Petition 870190103851, of 10/15/2019, p. 30/96
25/75 maps, to the first DRB, a data packet in the forwarded data packets that does not include a flow identifier.
[0113] After the first access network device maps some or all of the data packets forwarded to the first DRB, the first access network device sends the corresponding data packets to the terminal on the first DRB, for example, sends, in the first DRB, some or all of the data packets including flow identifiers in the forwarded data packets and all data packets including no flow identifiers in the forwarded data packets.
[0114] Optionally, in an implementation of this request, the method additionally includes: mapping, by the first access network device, to a second DRB based on a second mapping relationship, at least one data packet in the forwarded data packets including a flow identifier other than the data packet mapped to the first DRB, where the second mapping relationship is a mapping relationship between a flow and a DRB on the first access network device.
[0115] The second mapping relationship may include a correspondence between a flow identifier for each flow and a DRB on the first access network device. The first access network device can configure the mapping relationship between a stream and a DRB based on a QoS requirement, and establish the second DRB based on the mapping relationship. Such DRB established through an access network device based on a mapping relationship that is configured by the access network device between a stream and a DRB can also be referred to as a new DRB (new DRB). The QoS requirement includes a QoS parameter. When an automatic switch between access network devices is carried out via a direct interface, the QoS parameter can be configured via a source access network device and sent by the device source network device to a target access network device. When an automatic switch between access network devices is carried out over a main network, the QoS parameter can be sent from an originating base station to a main network device and then sent by the network device main for a
Petition 870190103851, of 10/15/2019, p. 31/96
26/75 target access network device. The main network device can modify the QoS parameter.
[0116] The first access network device can send data packets including flow identifiers in the forwarded data packets separately, in the first DRB and the second DRB, for example, send some packets to the terminal in the first DRB data that includes flow identifiers, and send the other data packets that include flow identifiers to the terminal in the second DRB. Specifically, the first access network device can send, to the terminal in the first DRB, a PDCP layer data packet including a flow identifier and to which a sequence number is allocated in the forwarded data packets, and send, for the terminal in the second DRB, a PDCP layer data packet including a flow identifier and for which no sequence number is allocated in the forwarded data packets.
[0117] Specifically, an SDAP entity of the first access network device can route data packets that include flow identifiers separately to different DRBs.
[0118] It can be understood that the second DRB can be the same or different from the first DRB. If the first mapping relation is the same as the second mapping relation, the first DRB is the same as the second DRB. Specifically, a DRB from the first access network device can be used first as a reflected DRB to send a received forwarded data packet and then used as a new DRB to send a received data packet from a main network . The same DRB is divided into the reflected DRB and the new DRB in a temporal dimension. In other words, different mapping relationships between a stream and a DRB can be used for different data packets received at different times. If the first mapping relationship is different from the second mapping relationship, the first DRB and the second DRB can be two independently established DRBs.
[0119] Optionally, in an implementation of this request, if the number of second DRBs is less than the number of first DRBs, and the first DRB is different from the second DRB, after the completion of the data packet in the first DRB, the first device
Petition 870190103851, of 10/15/2019, p. 32/96
27/75 access network and the terminal can release the first DRB, so that the overhead of the terminal and the first access network device can be reduced. Specifically, the first access network device can notify the terminal to release the first DRB. The terminal receives, from the first access network device, a notification message to instruct the terminal to release the first DRB, and releases a configuration from the first DRB. After receiving the notification message, the terminal can confirm that the sending of the downlink data packet in the first DRB has been completed. The notification message can be considered as an end marker, used to indicate that the transmission of the downlink data packet in the first DRB ends.
[0120] Optionally, the first access network device can send the second mapping relationship to the second access network device and the second access network device sends the second mapping relationship to the terminal.
[0121] Optionally, in an implementation of this request, the first access network device receives data packets forwarded through a tunnel between the first access network device and the second access network device. In a downlink direction, the tunnel between the first access network device and the second access network device can be established in different ways. A way of establishing a tunnel is not particularly limited in this embodiment of this application.
[0122] For example, the tunnel is a tunnel established on the basis of a DRB. The tunnel established on the basis of a DRB can be established between the third DRB of the second access device and the reflected DRB of the first access device, or it can be established between the third DRB and the new DRB of the first access device. One or more DRB-based tunnels can be established between the first access network device and the second access network device. The tunnel established on the basis of a DRB can be used to transmit the PDCP layer data packet.
[0123] Optionally, the first access network device can map, to the first DRB, a data packet that does not include a flow identifier that is received through the tunnel established on the basis of a DRB, and
Petition 870190103851, of 10/15/2019, p. 33/96
28/75 map, to the second DRB, a data packet including a flow identifier that is received through the tunnel established based on a DRB.
[0124] For another example, the tunnel is a tunnel established on the basis of a session. The tunnel established on the basis of a session can also be referred to as a tunnel established on the basis of an SDAP entity, and the tunnel is established between the SDAP entity of the first access device and an SDAP entity of the second access network device which are corresponding to the same session.
[0125] The tunnel established on the basis of a session can be used to transmit a data packet carrying a flow identifier for which no sequence number is allocated in the data packets forwarded on all DRBs in the session.
[0126] Optionally, the first access network device routes, to the first DRB through the SDAP entity, a PDCP layer data packet that is received from the tunnel established on the basis of a session and for which a number of sequence is allocated, and routes, to the second DRB, a PDCP layer data packet to which no sequence number is allocated or the SDAP layer data packet.
[0127] For another example, the tunnel includes a tunnel established on the basis of a DRB and a tunnel established on the basis of a session.
[0128] Optionally, the tunnel established on the basis of a DRB is used to transmit the PDCP layer data packet, and the tunnel established on the basis of a session is used to transmit the SDAP layer data packet.
[0129] Optionally, the tunnel established on the basis of a DRB is used to transmit a data packet that is cached in a PDCP layer of the second access network device, and for which a sequence number is allocated. A session-based tunnel is used to transmit the data packet in the forwarded data packets that carry a flow identifier, including the SDAP layer data packet from the second access network device, and / or a packet of data. data carrying a stream identifier to which no sequence number is allocated which is cached at the PDCP layer of the second access network device.
Petition 870190103851, of 10/15/2019, p. 34/96
29/75 [0130] Optionally, the first access network device can map, for the first DRB, a data packet received through the tunnel established based on a DRB, and map, for the second DRB, a data packet received through the tunnel established on the basis of a session.
[0131] In this embodiment of this request, the SDAP layer data packet includes a data packet cached at the SDAP layer, and the PDCP layer data packet includes a data packet cached at the PDCP layer.
[0132] It can be understood that the first access network device by simultaneously establishing a tunnel and a DRB. For example, in an automatic change scenario, if an automatic change request message sent by the second access network device to the first access network device includes information necessary to establish a tunnel and information necessary to establish a DRB, the first Access network device can perform a corresponding operation after receiving related information.
[0133] According to the data transmission method provided in this modality of this request, the first access network device receives data packets forwarded from the second access network device, and the first access network device can map, to the first DRB established by the first access network device, at least one data packet in the forwarded data packets that includes a flow identifier. The first DRB corresponds to the DRB of the second access network device. In addition, for better network performance, the first access network device establishes the second DRB. The second DRB is used to transmit the data packet having a stream identifier in the forwarded data packets different from the data packet mapped to the first DRB, and the second DRB meets the mapping relationship that is between a stream and a DRB and which is configured by the first access network device. Therefore, forwarded data packets can be transmitted in a variety of flexible transmission ways on different DRBs, and a data packet transmission way can be selected based on a real state of the network, to avoid the problem: In an automatic changeover or dual connectivity or another scenario, a data packet is
Petition 870190103851, of 10/15/2019, p. 35/96
30/75 lost or transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0134] FIG. 3 is a schematic flow chart of a data transmission method, according to an embodiment of this request.
[0135] Similar to the data transmission method provided in the embodiment shown in FIG. 2, the data transmission method provided in this modality is applicable to several scenarios that have a data forwarding process between base stations, such as an automatic switching process or a dual terminal connectivity process. The details are not described.
[0136] The method includes the following steps.
[0137] S301. A first access network device receives forwarded data packets (or a forwarded data packet) from a second access network device.
[0138] For a detailed description of the forwarded data packets, consult the related contents in the modality shown in FIG. 2. The details are not described again in this report.
[0139] S302. The first access network device maps, to a first DRB, a data packet in the forwarded data packets that does not include a flow identifier, where the first DRB corresponds to a DRB of the second access network device (briefly referred to as “third DRB”).
[0140] Specifically, the first DRB and the third DRB serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device.
[0141] Optionally, the first access network device receives the first mapping relation from the second access network device.
[0142] S303. The first access network device maps, to a second DRB based on a second mapping relationship, a data packet in the forwarded data packets that includes an identifier
Petition 870190103851, of 10/15/2019, p. 36/96
31/75 flow, where the second mapping relationship is a mapping relationship between a flow and a DRB on the first access network device.
[0143] The first DRB is a reflected DRB, and the second DRB is a new DRB. For the related detailed description, see the related contents in the modality shown in FIG. 2. The details are not described again in this report. It can be understood that the first DRB and the second DRB are established separately by the first access network device, and there is no sequence of steps to establish the first DRB and establish the second DRB by the first access network device.
[0144] For a detailed description of the first mapping relation and the second mapping relation, consult the related contents in the modality shown in FIG. 2. The details are not described again in this report.
[0145] Optionally, the first access network device routes, through an SDAP entity to the second DRB, the data packet in the forwarded data packets that includes a flow identifier.
[0146] It can be understood that there is no sequence for the execution of step S302 and step S303. For example, S302 can be performed before S303, or S303 can be performed before S302, or the two steps S302 and S303 can be performed simultaneously. This is not particularly limited in this embodiment of this application.
[0147] Optionally, in an implementation of this request, the method additionally includes: sending, by the first network device accessing a terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier and for which a sequence number is allocated; and sending, by the first terminal access network device in the second DRB, a data packet in the forwarded data packets that includes a flow identifier and for which no sequence number is allocated. The data packet can be a PDCP layer data packet and the sequence number is a PDCP SN.
[0148] Optionally, in an implementation of this request, the method additionally includes: send, by the first access network device
Petition 870190103851, of 10/15/2019, p. 37/96
32/75 to a terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier; and sending, through the first terminal access network device in the second DRB, a data packet in the forwarded data packets that includes a flow identifier.
[0149] Optionally, in an implementation of this request, if the number of second DRBs is less than the number of first DRBs, and the first DRB is different from the second DRB, after the completion of the data packet in the first DRB, the first access network device and the terminal can separately release the first DRB, so that the overhead costs of the terminal and the first access network device can be reduced. For the related detailed description, see the related contents in the modality shown in FIG. 2. The details are not described again in this report.
[0150] Optionally, the first access network device can send the second mapping relationship to the second access network device and the second access network device sends the second mapping relationship to the terminal.
[0151] Optionally, in an implementation of this request, the first access network device receives data packets forwarded through a tunnel between the first access network device and the second access network device. In a downlink direction, the tunnel between the first access network device and the second access network device can be established in different ways.
[0152] For example, the first access network device receives data packets forwarded from the second access network device through a tunnel established on the basis of a DRB and a tunnel established on the basis of a session.
[0153] Optionally, the tunnel established on the basis of a DRB is used to transmit a data packet that is cached in a PDCP layer of the second access network device, and for which a sequence number is allocated. The session-based tunnel is used to transmit the data packet in the forwarded data packets that carry a flow identifier, including an SDAP layer data packet from the second access network device, and / or a packet of data.
Petition 870190103851, of 10/15/2019, p. 38/96
33/75 data that is cached in the PDCP layer of the second access network device, which carries a flow identifier and for which no sequence number is allocated.
[0154] For another example, the first access network device receives data packets forwarded from the second access network device through a tunnel established on the basis of a DRB.
[0155] For another example, the first access network device receives, from the second access network device through a tunnel established on the basis of a session, the data packet in the forwarded data packets that includes an flow.
[0156] Optionally, the first access network device routes, to the first DRB through the SDAP entity, a PDCP layer data packet that is received from the tunnel established on the basis of a session and for which a number sequence data is allocated, and routes, to the second DRB, a PDCP layer data packet to which no sequence number is allocated or an SDAP layer data packet.
[0157] For a detailed description of the various previous tunnels, consult the related contents in the modality shown in FIG. 2. The details are not described again in this report.
[0158] Optionally, after completing the sending of the forwarded data packet mapped to the first DRB, the first access network device can release the first DRB, to save a resource. For a detailed description of the release of the first DRB, consult the related contents in the modality shown in FIG. 2. The details are not described again in this report.
[0159] According to the data transmission method provided in this modality of this request, on the premise that each access network device can independently define a mapping relationship between a flow and a DRB, the data packet that has a flow identifier is mapped to the second DRB for transmission, and the data packet that does not have the flow identifier is mapped to the first DRB for transmission. Therefore, a way of transmitting a data packet can be selected based on a real state of the network, to avoid the problem: In an automatic switch or dual connectivity or other scenario, a data packet is
Petition 870190103851, of 10/15/2019, p. 39/96
34/75 lost or transmitted repeatedly by the fact that each access network device independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0160] FIG. 4 is a schematic flow chart of a data transmission method, according to an embodiment of this request.
[0161] The data transmission method provided in this modality is applicable to several scenarios that have a data forwarding process between base stations, such as an automatic switching process or a dual terminal connectivity process. The details are not described.
[0162] The method includes the following steps.
[0163] S401. A first access network device receives a forwarded data packet (or forwarded data packets) from a second access network device, where the forwarded data packet includes a flow identifier, and the forwarded data packet includes an out-of-service data packet received by the second access network device from a terminal.
[0164] Specifically, in an uplink direction, the forwarded data packet is an out-of-service PDCP layer data packet received by the second access network device from the terminal. For example, if a sequence number from a last PDCP SDU received sequentially by the second access network device is an SN, in other words, PDCP SDUs whose sequence numbers (..., SN-1, SN) are less than that the SN is received sequentially, a PDCP SDU is the order that is received by the second access network device and whose sequence number is greater than the SN is a data packet that needs data forwarding. For example, data forwarding is required for PDCP SDUs whose sequence numbers are SN + 3, SN + 4, and SN + 6 and which are received by the second access network device after receiving the PDCP SDU with the number of sequence being the SN.
[0165] S402. The first access network device sends the received forwarded data packet (or forwarded data packets) to a primary network device.
Petition 870190103851, of 10/15/2019, p. 40/96
35/75 [0166] Optionally, the first access network device receives the data packet forwarded through a tunnel between the first access network device and the second access network device. The tunnel can be a tunnel that is established between the first access network device and the second access network device based on a DRB. For the tunnel, consult the related descriptions of the tunnel established based on a DRB in another modality of this order. The details are not described again.
[0167] Optionally, in an implementation of this request, the method additionally includes: receiving, by the first access network device, uplink data packets from the terminal, where the uplink data packets include at least one type the following data packets: a PDCP layer data packet that is unsuccessfully sent by the terminal to the second access network device and to which a sequence number is allocated; a terminal PDCP layer data packet, to which no sequence number is allocated; and an SDAP layer data packet from the terminal.
[0168] Optionally, after the terminal finishes sending the uplink data packet in a first DRB, the terminal can request the first access network device to release the first DRB. The first access network device may consider that a request sent by the terminal to release the first DRB is a final marker, and the request is used to indicate that the transmission of the uplink data packet in the first DRB ends.
[0169] After accessing the first access network device, the terminal can send uplink data packets to the first access network device in different ways of sending.
[0170] Optionally, the first access network device receives the uplink data packets in the first DRB.
[0171] Optionally, the first access network device receives the uplink data packets in a second DRB.
[0172] Optionally, the first access network device receives, in the first DRB, a PDCP layer data packet from the terminal, to which a sequence number is allocated in the link data packets
Petition 870190103851, of 10/15/2019, p. 41/96
Ascending 36/75; and the first access network device receives, in a second DRB, the PDCP layer data packet from the terminal, for which no sequence number is allocated in the uplink data packets and / or the layer data packet Terminal SDAP on uplink data packets.
[0173] Optionally, the first access network device receives a PDCP layer data packet from the terminal in the uplink data packets in the first DRB; and the first access network device receives the SDAP layer data packet from the terminal in the uplink data packets in a second DRB.
[0174] The first DRB is a reflected DRB, and the second DRB is a new DRB. For the related detailed description, see the related contents in another modality of this request. The details are not described again in this report.
[0175] According to the data transmission method provided in this modality of this request, in the direction of the uplink, the first access network device receives, from the second access network device, the forwarded data packet that includes a flow identifier. The forwarded data packet includes the out-of-service data packet received by the second access network device from the terminal. After the forwarding of the forwarded data packet is complete, the terminal can send the uplink data packets to one side of the network in various flexible transmission ways on different DRBs, and a data packet transmission way can be selected with based on a real state of the network, to avoid the problem: In an automatic switch or dual connectivity or other scenario, a data packet is lost or is transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a flow and a DRB. This improves the continuity of the terminal service and improves the quality of communication.
[0176] FIG. 5 is a schematic flow chart of a data transmission method, according to an embodiment of this request.
[0177] Similar to the data transmission method provided in the modality shown in FIG. 2, the data transmission method provided
Petition 870190103851, of 10/15/2019, p. 42/96
37/75 in this modality is applicable to several scenarios that have a data forwarding process between base stations, such as an automatic switching process or a terminal double connectivity process. The details are not described.
[0178] The method includes the following steps.
[0179] S501. A second access network device generates a forwarding data packet that includes a flow identifier (or forwarding data packets that includes flow identifiers).
[0180] S502. The second access network device sends, for a first access network device, the forwarding data packet that includes a flow identifier (or forwarding data packets that include flow identifiers).
[0181] Optionally, in a downlink direction, the forwarding data packet includes at least one type of the following data packets: a PDCP layer data packet from the second access network device, to which a sequence number is allocated, and for which there is no acknowledgment of receipt it is obtained from a terminal; a PDCP layer data packet from the second access network device to which no sequence number is allocated; and a SDAP Service Data Adaptation Protocol layer data packet from the second access network device.
[0182] Optionally, in the downlink direction, the second access network device additionally sends a data packet for routing to the first access network device that does not include a flow identifier (or data packets for routing) which does not include a flow identifier).
[0183] Optionally, in the downlink direction, the second access network device can send data packets for forwarding to the first access network device through different types of tunnels. For a detailed description of several tunnels and transmission of data packets for routing through the various tunnels, consult the contents listed in another modality of this request. The details are not described again in this report.
[0184] It can be understood that in the direction of downlink, the
Petition 870190103851, of 10/15/2019, p. 43/96
The first access network device can send downlink data packets to the terminal that includes the forwarded data packet. Specifically, after the second access network device sends the data packet for forwarding to the first access network device, the first access network device can map the data packet forwarded to a corresponding DRB based on such a factor like the content (for example, if the forwarded data packet has a flow identifier, or if a sequence number is allocated to the forwarded data packet) of the forwarded data packet or a type of tunnel that carries the data packet forwarded, to transmit the forwarded data packet. For a detailed description of the mapping of the data packet sent to the corresponding DRB by the first access network device, consult the related contents in another modality of this request. The details are not described again in this report. Then, the first access network device sends another downlink data packet obtained from a main network to the terminal.
[0185] Optionally, in an implementation of this request, in the downlink direction, a PDCP entity of the second access network device obtains the flow identifier, so that the second access network device can add the flow identifier to the forwarding data packet, and generating the forwarding data packet that includes the flow identifier, and then the first access network device analyzes the forwarded data packet to obtain the flow identifier.
[0186] Optionally, the second access network device obtains the data packet flow identifier based on a correspondence between a service access point (SAP) and the flow identifier. Specifically, the second access network device establishes one or more SAPs between an SDAP entity and a PDCP entity, and the PDCP entity separately caches a PDCP PDU or a PDCP SDU based on an SAP and a flow identifier. Each SAP is corresponding to a flow. When forwarding data, the second access network device can send the PDCP PDU or PDCP SDU to the SAP-based SDAP entity, and then the SDAP entity can obtain the
Petition 870190103851, of 10/15/2019, p. 44/96
39/75 flow identifier of the PDCP layer data packet based on a correspondence between SAP and a flow. Alternatively, the PDCP entity can obtain the flow identifier based on SAP information. The forwarded data packet includes a PDCP PDU and a PDCP SDU, and a PDCP SDU that carries a sequence number is generated after processing such as removing or decrypting the header in the protocol to be performed on the PDCP PDU.
[0187] Optionally, the second access network device obtains the data packet flow identifier based on a data packet cache location. Specifically, an SDAP entity of the second access network device sends the data packet flow identifier to a PDCP entity, and the PDCP entity establishes a match between the flow identifier and the data packet cache location. For example, the PDCP entity can cache the PDCP SDU received based on the flow identifier. Then, the second access network device obtains the cache location of the forwarded data packet. The cache location of the forwarded data packet matches the flow identifier of the forwarded data packet. The second access network device obtains the data packet flow identifier based on the cache location of the data packet. Optionally, an SDAP layer of the second access network device additionally includes indication information, and indication information is used to indicate whether a PDCP layer adds a flow identifier to a PDCP PDU and sends, via an air interface, the PDCP PDU that includes the flow identifier. For example, if the indication information indicates that no flow identifier has been added, the PDCP PDU is generated by removing the flow identifier data from an SDAP header. Because the PDCP PDU does not include a flow identifier, data overhead is reduced.
[0188] Optionally, in an automatic change preparation process, an SDAP entity from the second access network device can add a flow identifier to a received data packet, and indicate that the flow identifier is used only for one process automatic switching. Therefore, the first access network device can restore the
Petition 870190103851, of 10/15/2019, p. 45/96
40/75 flow identifier based on the received forwarded data packet.
[0189] Optionally, in an automatic change preparation process, an SDAP entity of the second access network device can add a flow identifier to a received data packet. For example, when the second access network device freezes a transmission state, the SDAP entity starts adding flow identifiers to all data packets to be sent to a PDCP layer, and freezing the transmission state means that the second access network device no longer sends data to the terminal. Therefore, the first access network device can restore the flow identifier based on the received forwarded data packet.
[0190] Optionally, the second access network device determines the flow identifier based on a sequence number included in the forwarded data packet. Specifically, an SDAP entity of the second access network device caches the data packet, configures an SDAP sequence number for the cached data packet, and sends the data packet for which it is a PDCP entity. the SDAP sequence number is configured. If the PDCP entity successfully sends a data packet that includes a PDCP SN to the first access network device, the PDCP entity sends an indication to an SDAP layer. After receiving the indication, the SDAP layer deletes a data packet corresponding to the data packet that includes the PDCP SN. A data packet cached in the SDAP layer has a flow identifier, a data packet sent by the SDAP entity to the PDCP entity includes an SDAP sequence number, and the SDAP sequence number corresponds to the flow identifier. Therefore, the SDAP entity of the second access network device obtains the data packet flow identifier by matching it based on the SDAP sequence number of the data packet received from the PDCP layer.
[0191] Optionally, in an uplink direction, the forwarded data packet includes an out-of-service data packet received by the second access network device from the terminal. All data packets forwarded in the uplink direction include flow identifiers. The second access network device can send the
Petition 870190103851, of 10/15/2019, p. 46/96
41/75 data packet forwarded in the uplink direction to the first access network device through a tunnel established on the basis of a DRB. The details are not described.
[0192] It can be understood that in the uplink direction, after the second access network device sends the data packet forwarded to the first access network device, the first access network device can send the data packet forwarded to the main network. After accessing the first access network device, the terminal can send uplink data packets to the first access network device on different DRBs. For a detailed description of the sending, by the terminal, the uplink data packets to the first access network device, consult the related contents in another modality of this request. The details are not described again in this report.
[0193] FIG. 6 is a schematic signaling flowchart of a data transmission method, according to an embodiment of this request.
[0194] In the embodiment shown in FIG. 6, an example in which a terminal is automatically switched from a source base station to a destination base station is used to describe the data transmission method provided in this embodiment of this application. It can be understood that the embodiment shown in FIG. 6 is a further explanation and description of the modalities shown in FIG. 2 to FIG. 5. The home base station is an example of the second access network device in these embodiments shown in FIG. 2 to FIG. 5. The destination base station is an example of the first access network device in these embodiments shown in FIG. 2 to FIG. 5. Mutual reference can be made between the modalities provided in this application.
[0195] The method includes the following steps.
[0196] S601. A terminal sends a measurement report to an originating base station.
[0197] S602. The originating base station determines, based on the measurement report received, to trigger an automatic switching procedure.
[0198] S603. The originating base station sends a first report
Petition 870190103851, of 10/15/2019, p. 47/96
42/75 mapping to a target base station.
[0199] The first mapping relationship is a mapping relationship that is between a flow and a DRB and that is configured by the originating base station. For a detailed description of the first mapping relationship, consult the related contents of another modality of this request. The details are not described again in this report.
[0200] Optionally, the first mapping relationship is included in the signaling or a message that is sent by the originating base station to the destination base station in an automatic change process, for example, an automatic change request message . This is not limited in this mode of this application.
[0201] Optionally, after the destination base station receives the automatic change request message sent by the originating base station, the destination base station can establish a DRB between the destination base station and the terminal, including a reflected DRB (i.e., the first DRB in the embodiment shown in FIG. 2 or FIG. 3) to maintain a transmission status of a DRB from the originating base station. In addition to the reflected DRB, the destination base station can additionally establish a new carrier (that is, the second DRB in the mode shown in FIG. 2 or FIG. 3) based on a mapping relationship that is between a flow and a DRB and that is configured by the target base station. For a detailed description of the reflected DRB and the new DRB, consult the related contents in another form of this request. The details are not described again in this report.
[0202] S604. The target base station sends a second mapping relationship to the source base station.
[0203] The second mapping relationship can be included in the signaling or a message that is sent by the destination base station to the originating base station in the automatic change process, for example, an automatic change request response message . This is not limited in this mode of this application.
[0204] The second mapping relationship is a mapping relationship that is between a flow and a DRB and that is configured by the destination base station. For a detailed description of the second
Petition 870190103851, of 10/15/2019, p. 48/96
43/75 mapping, consult the related contents of another modality of this request. The details are not described in this report.
[0205] S605. The originating base station sends an automatic change command to the terminal.
[0206] The automatic change command can include the second mapping relation, so that the terminal can obtain the second mapping relation.
[0207] The second mapping relation can be the same or different from the first mapping relation. Specifically, because each access network device independently configures a mapping relationship between a DRB and a flow based on a flow QoS requirement, the mapping relationship that is between a DRB and a flow and which is configured the destination base station can be the same or different from the mapping relationship that is between a DRB and a stream and that is configured by the originating base station.
[0208] Optionally, the response message and the automatic change command additionally include a third mapping relationship, and the third mapping relationship is a correspondence between the reflected DRB configured by the target base station and the DRB configured by the destination station. target base.
[0209] S606. The originating base station sends a transmission status from the aerial interface of a PDCP layer to the destination base station.
[0210] The transmission state of the PDCP layer overhead interface means a sending state and a receiving state of a PDCP layer data packet in the DRB of the originating base station. A transmission state of an uplink data packet includes a sequence number of a first lost PDCP SDU, and a receiving state of a PDCP SDU between the first lost PDCP SDU and a last received PDCP SDU. The receiving state specifically means whether a data packet is received. A downlink data packet transmission state includes a sequence number from an upcoming PDCP SDU to which the target base station needs to allocate a sequence number and the sequence number includes a PDCP SN and an HFN.
Petition 870190103851, of 10/15/2019, p. 49/96
44/75 [0211] S607. The originating base station sends forwarding data packets (or a forwarding data packet) to the destination base station.
[0212] The forwarding data packets include a forwarding data packet, and / or a forwarding data packet. For a detailed description of the forwarded data packets, consult the contents related to these modalities shown in FIG. 2 to FIG. 4. The details are not described again in this report.
[0213] Specifically, the originating base station can send the data packets for routing to the destination base station through a tunnel between the originating base station and the destination base station. For various tunnels and specific ways of establishing a tunnel, consult the contents related to these modalities shown in FIG. 2 to FIG. 5. The details are not described again in this report.
[0214] In this embodiment, a PDCP entity of the originating base station obtains a flow identifier from the data packet, so that the originating base station can add the flow identifier to the data packet for forwarding, and then , the destination base station can map the data packet forwarded to a corresponding DRB based on the flow identifier. For a detailed description of the generation, by the originating base station, of the data package that includes the flow identifier, consult the contents related to the modality shown in FIG. 5. The details are not described again in this report.
[0215] S608. The terminal accesses the destination base station.
[0216] S609. The destination base station performs the path switch.
[0217] Optionally, the method additionally includes: notifying, by the destination base station, a control plan management network element of a main network to notify a user plan network element to send a subsequent data packet related to the terminal for the target base station.
[0218] Optionally, in an implementation of this request, after the terminal is automatically switched to the destination base station, the
Petition 870190103851, of 10/15/2019, p. 50/96
45/75 method additionally includes: S610. The terminal performs data communication with the destination base station.
[0219] Data communication includes uplink data transmission and / or downlink data transmission.
[0220] Specifically, in an uplink data transmission process or a downlink data transmission process, forwarded data packets received through different types of tunnels are transmitted in different ways. This is not particularly limited in this embodiment of this application. In addition, in the downlink data transmission process, the destination base station may send the data packet forwarded in the downlink direction and another downlink data packet received from the main network to the terminal. . In the uplink data transmission process, the destination base station can send the data packet forwarded in the uplink direction and another uplink data packet received from the terminal to the main network. The transmission of the forwarded data packet takes precedence over that of the other uplink data packet received from the terminal or the other downlink data packet received from the main network. Optionally, the uplink data packet and the downlink data packet can be transported in the same DRB. In other words, a bidirectional DRB provides an uplink service and a downlink service. Alternatively, the uplink data packet and the downlink data packet can be carried on different DRBs.
[0221] In the downlink direction, the destination base station can send downlink data packets that include forwarded data packets to the terminal on the first DRB or second DRB.
[0222] For example, when forwarding data packets are sent to the destination base station through a DRB-based tunnel and a session-based tunnel, a specific way in which the base station destination sends the data packets to the terminal may include the following:
Petition 870190103851, of 10/15/2019, p. 51/96
46/75 [0223] If the second mapping relation is the same as the first mapping relation, the destination base station can send the data packets forwarded to the terminal in the first DRB and then after completing the sending the forwarded data packets, send, still in the first DRB, another downlink data packet received from the main network through an SDAP layer.
[0224] If the second mapping relation is different from the first mapping relation, the destination base station can send a data packet received by the destination base station through the established tunnel to the terminal in the first DRB based on a DRB; and sending, to the terminal on the second DRB, a data packet received by the destination base station through the tunnel established on the basis of a session.
[0225] Optionally, the destination base station sends, to the terminal in the second DRB, a data packet in the forwarded data packets that includes a flow identifier, and the destination base station sends, to the terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier.
[0226] Optionally, the destination base station can send, to the terminal in the first DRB, a PDCP SDU in the forwarded data packets, to which a sequence number is allocated, and the destination base station sends, to the terminal in the second DRB, a PDCP SDU that includes a flow identifier and for which no sequence number is allocated. The destination base station can additionally send an SDAP layer data packet from the originating base station to the terminal on the second DRB. It can be understood that the first DRB can be used to transmit a data packet that has a flow identifier or a data packet that does not have the flow identifier. Therefore, any PDCP SDU that has a sequence number can be transmitted in the first DRB regardless of whether the PDCP SDU includes a flow identifier.
[0227] Optionally, the originating base station can allocate a sequence number to a PDCP SDU which is cached in the PDCP layer and for which no sequence number is allocated, and send, to the destination base station like some of the data packets for routing through the tunnel established on the basis of a DRB, the PDCP
Petition 870190103851, of 10/15/2019, p. 52/96
47/75
SDU to which the sequence number is allocated. Then, in a subsequent communication process, the destination base station can directly transmit, in the first DRB, the PDCP SDU to which the sequence number is allocated, without allocating a sequence number to the PDCP SDU. This simplifies a procedure and improves transmission efficiency.
[0228] For another example, when forwarding data packets are sent to the destination base station through a tunnel based on a session, the destination base station can route, to the first DRB through a SDAP entity, a PDCP layer data packet in the data packets to which a sequence number is allocated, and send, to the terminal in the first DRB, the PDCP layer data packet to which the sequence number is allocated. The destination base station routes, to the second DRB through the SDAP entity, remaining data packets such as a data packet cached in an SDAP layer and / or a PDCP layer data packet for which no number of sequence is allocated, and sends the remaining data packets to the terminal in the second DRB. Optionally, the SDAP entity can determine a plurality of second DRBs based on the mapping relationship between a stream and a DRB at the destination base station, and send the remaining data packets in the plurality of second DRBs, to transmit the data packets remaining to the terminal. The PDCP layer data packet in the forwarded data packets to which the sequence number is allocated can carry an identifier from a third DRB, and the destination base station can forward, to the first corresponding DRB based on a relationship of mapping between the third DRB and the first DRB, the received data packet to which the sequence number is allocated.
[0229] For another example, when forwarding data packets are sent to the destination base station through one or more tunnels established on the basis of a DRB, a specific way in which the destination base station sends the packets data to the terminal includes the following:
[0230] If the first mapping relation is the same as the second mapping relation, the destination base station sends, to the
Petition 870190103851, of 10/15/2019, p. 53/96
48/75 terminal in the first DRB, the data packets received by the destination base station through the tunnel established on the basis of a DRB and then, after completing the sending of the forwarded data packets, it sends, still through the use of the first DRB, another data packet received from the main network through an SDAP layer.
[0231] Optionally, the originating base station can allocate a sequence number to a PDCP SDU which is cached in the PDCP layer and for which no sequence number is allocated, and send, to the destination base station like some of the forwarding data packets, the PDCP SDU to which the sequence number is allocated. The details are not described.
[0232] If the first mapping relation is different from the second mapping relation, the destination base station sends a data packet to the terminal in the first DRB that does not include a flow identifier in the received data packets by the destination base station through the tunnel established on the basis of a DRB, and the destination base station sends a data packet to the terminal in the second DRB that includes a flow identifier in the data packets received by the station destination base through the tunnel established on the basis of a DRB. Specifically, when two tunnels are established between the destination base station and the originating base station based on a DRB, a data packet transmitted through a tunnel established based on a third DRB from the originating base station and the first DRB is transmitted in the first DRB, and a data packet transmitted through a tunnel established based on the DRB of the originating base station and the second DRB is transmitted in the second DRB. When only one tunnel is established between the destination base station and the originating base station based on the third DRB of the originating base station and the first DRB, the destination base station can route, to the second DRB through from an SDAP entity, a data packet in the received data packets that includes a stream identifier, and transmits the data packet in the second DRB. In this implementation, another data packet that is included in the flow identifier is sent in the first DRB. In this implementation, the originating base station can obtain a stream identifier from a data packet for forwarding in a way that
Petition 870190103851, of 10/15/2019, p. 54/96
49/75 an SDAP entity sends the flow identifier to the PDCP layer during an automatic change, and indicates, in the forwarding data packet, that the flow identifier is used for the automatic change. Alternatively, the originating base station can generate, in another flow identifier, obtaining the way described in these modalities of this request, flow identifiers for all PDCP layer data packets that do not have PDCP SN, and forward to the station target base, the data packets that includes the stream identifier. The details are not described.
[0233] In this implementation, alternatively, the originating base station can generate, in the various flow identifiers that obtain ways described in this request, a flow identifier for a PDCP layer data packet for which no sequence number is allocated , and send the forwarding data packet that includes the flow identifier to the destination base station. The details are not described.
[0234] Optionally, if the forwarded data packets are PDCPs layer data packets to which no sequence number is allocated, some of the data packets include a flow identifier, and a remaining data packet will not include a data identifier. flow, the forwarded data packets will be sent to the terminal at the first DRB. This can improve the continuity and accuracy of data packet transmission. A data packet from a stratum stream without access that is presented in reflective QoS can be sent in the first DRB. Reflective QoS means that the flow is presented in uplink and downlink symmetry. For specificity, a flow in an uplink direction and a flow in an uplink direction have the same QoS, and a uplink traffic flow model (TFT) and an uplink traffic flow model. downlink are symmetric. For example, an uplink source address and a source port number are a uplink destination address and a destination port number, and an uplink destination address and a destination port number are one. downlink source address and a source port number. In this scenario, the access network device adds a flow identifier to an air interface data packet, and the terminal
Petition 870190103851, of 10/15/2019, p. 55/96
50/75 obtains, based on the received stream identifier and the 5 tuple information of the downlink data packet, the QoS of a stream in an uplink direction and a corresponding TFT.
[0235] In the uplink direction, the terminal can send uplink data packets that include forwarded data packets to the destination base station in the first DRB or second DRB.
[0236] Optionally, the uplink data packets sent by the terminal to the destination base station include data packets that require uplink continuous transmission, such as a PDCP SDU that cannot be transmitted by the terminal in the DRB of the originating base station and to which a sequence number is allocated, and a PDCP SDU that cannot be transmitted by the terminal in the DRB of the originating base station and to which no sequence number is allocated. All uplink data packets include flow identifiers.
[0237] Optionally, the destination base station receives the uplink data packets from the first DRB. Specifically, if the first mapping relation is the same as the second mapping relation, the terminal can continue to send a PDCP layer data packet in the first DRB. The PDCP layer data packet includes the unsuccessfully transmitted PDCP SDU to which the sequence number is allocated, and / or the unsuccessfully transmitted PDCP SDU to which no sequence number is allocated.
[0238] Optionally, the originating base station sends a status report (status report) to the terminal, and the terminal determines a data packet to be sent based on the status report. The status report can be a PDCP status report that indicates a receiving status of a PDCP SDU in the DRB reflected from the target base station and which is used to notify the terminal to send a PDCP SDU that is received incorrectly in a receiving side. If the target base station does not send the PDCP status report, the terminal can send all PDCP SDUs cached in the reflected DRB.
[0239] If the first mapping relation is different from the second mapping relation, the terminal may continue to send, in the
Petition 870190103851, of 10/15/2019, p. 56/96
51/75 first DRB, all data packets such as a PDCP SDU that is cached in a PDCP layer and for which a sequence number is allocated, and / or a PDCP SDU that is cached in the PDCP layer and for which no sequence number is allocated. After the terminal finishes sending the PDCPs layer data packet, an SDAP entity can route, to the second DRB for sending, another data packet such as a cached data packet on an SDAP layer. A terminal PDCP entity can notify the target base station's SDAP entity that the sending of the data packet is complete.
[0240] Optionally, the destination base station receives the uplink data packets from the second DRB. The way of receiving is applicable to a scenario in which the first mapping relation is different from the second mapping relation. Specifically, the terminal can sequentially send PDCP layer data packets corresponding to DRBs to an SDAP entity, including the unsuccessfully transmitted PDCP SDU to which a sequence number is allocated and / or the unsuccessful PDCP SDU transmitted to which no sequence number is allocated. Sequential sending means sending the data packets to an SDAP layer in a sequence of receiving the data packets through a PDCP layer from the SDAP layer. The SDAP entity is established based on a session, and all data packets sent to the SDAP entity include a flow identifier. The PDCP PDUs includes a data packet that was successfully received by the target base station. The terminal PDCP entity corresponding to the destination base station's DRB performs an operation such as removing or decrypting the sequence number on the PDCP PDUs, to convert the PDCP PDUs into PDCP SDUs. Alternatively, the endpoint SDAP entity that corresponds to the destination base station's DRB removes the sequence numbers from the PDCP PDUs. The terminal's SDAP entity routes, to a corresponding DRB (i.e., the second DRB) based on the second mapping relationship, the data packets received from the PDCP layer. The SDAP entity first sends data packets received from the PDCP layer to the second DRB and then sends a data packet received from the upper DRB to the second DRB. It can be understood that in this
Petition 870190103851, of 10/15/2019, p. 57/96
In this scenario, the destination base station and the second access network device cannot perform a data forwarding process in the uplink direction.
[0241] Optionally, the destination base station receives, from the first DRB, a PDCP layer data packet to which a sequence number is allocated in the uplink data packets, and receives, from the second DRB , a PDCP layer data packet for which no sequence number is allocated in the uplink data packets and / or an SDAP layer data packet in the uplink data packets. The receipt method is applicable to a scenario in which the first mapping relation is different from the second mapping relation. Specifically, the terminal can continue to send, in the first DRB, the PDCP SDU unsuccessfully transmitted to which the sequence number is allocated. The originating base station can send a status report to the terminal, and the terminal determines a data packet to be sent based on the status report. The details are not described. In addition, the terminal can sequentially send the PDCP SDUs to an SDAP entity. All data packets sent to the SDAP entity include flow identifiers. The SDAP entity routes, to a corresponding DRB based on the second mapping relationship, the data packets received from a PDCP layer. The SDAP entity first sends the data packets received from the PDCP layer to the corresponding DRB and then sends a data packet received from the upper layer to the corresponding DRB.
[0242] In an implementation of this request, when an unacknowledged mode, UM service such as a cellular transmission service or an IP call service is performed by an air interface, information about an interface transmission status overhead of a service-related data packet does not need to be transferred between the destination base station and the originating base station. Specifically, in the uplink direction, the originating base station sends a received data packet successfully to the main network, without performing data forwarding. The terminal accesses the destination base station, and the terminal transmits a data packet in the new DRB based on the second
Petition 870190103851, of 10/15/2019, p. 58/96
53/75 mapping configured by the target base station. This scenario is applicable to a scenario in which the first mapping relation is the same or different from the second mapping relation. In the downlink direction, the originating base station forwards, to the destination base station, a data packet that has not been transmitted and a new data packet received from the main network. Compared to an acknowledged mode service, in the unrecognized mode service, a forwarding data packet that does not include a PDCP SDU that is in the DRB of the originating base station and for which a number of sequence is allocated. In other words, the originating base station does not need to send a PDCP SDU unsuccessfully sent to the originating base station's DRB to the destination base station. Another behavior of the destination base station or of the originating base station is compatible with that of a downlink data transmission process in AM mode. The details are not described.
[0243] Optionally, after receiving the uplink data packets, the destination base station delivers first, in ascending order of PDCP SNs to the main network, PDCP SDUs that are in the uplink data packets and to which sequence numbers are allocated and then delivers the PDCP SDU that is in the uplink data packets to the main network and for which no sequence number is allocated.
[0244] In an implementation of this request, in a process of transmitting data packets in the downlink or uplink direction, the data packets that belong to the same stream can be transmitted in different DRBs. For example, some data packets in the same stream are transmitted in the reflected DRB, and a remaining data packet is transmitted in the new DRB. The reflected DRB and the new DRB are distinguished only in a temporal dimension. For example, a data packet first transmitted to the destination base station is transmitted on the reflected DRB, and a data packet later transmitted to the destination base station is transmitted on the new DRB. In this case, data packets in the same stream can be transmitted sequentially in one of the following ways.
Petition 870190103851, of 10/15/2019, p. 59/96
54/75 [0245] Optionally, a transmission end controls a data packet transmission sequence. Specifically, after the sending of forwarded data packets in the first DRB is completed, the second DRB is instructed to send another data packet. Optionally, a PDCP entity corresponding to the first DRB can notify a PDCP entity corresponding to the second DRB. If the first DRB includes data packets from a plurality of streams, the first DRB can notify a second DRB to which each stream is mapped. Alternatively, after the sending of data packets forwarded in the first DRB is completed, an SDAP entity is notified. For example, a PDCP entity from the first DRB may notify the corresponding SDAP entity that the sending of forwarded data packets has been completed. If the PDCP entity corresponding to the first DRB can discover a stream identifier, the PDCP entity can notify the corresponding SDAP entity that the sending of data packets that are in the forwarded data packets and that belong to a stream has been completed. If the SDAP entity discovers that the forwarded data packets sent by the PDCP entity are successfully sent, the SDAP entity begins to route a data packet from a stream corresponding to the second corresponding DRB, and the data packet from the corresponding stream is a packet. SDAP layer data in a stream that is completed in the first DRB.
[0246] Optionally, a receiving end controls a data packet transmission sequence. Specifically, the receiving end receives data packets in the same stream from the first DRB and the second DRB, and the receiving end can distinguish between data packets from different DRBs based on a final marker, to classify the data packets received from different DRBs. For example, the receiving end delivers first, to an upper layer protocol layer entity, a data packet that is from the stream and that is received from the first DRB and then inbound to the layer entity upper layer protocol, a data packet that is from the stream and that is received from the second DRB. The final marker is used to indicate that the packet data transmission in the first DRB is finished. The final marker can be an independent data package or
Petition 870190103851, of 10/15/2019, p. 60/96
55/75 control pack, for example, an independent SDAP layer or PDCP layer data pack or control pack. Alternatively, the final marker may indicate that a specific data package such as a PDCP PDU is an end marker.
[0247] It can be understood that in the downlink direction, the transmission end is a side of the network, for example, the destination base station, and the receiving end is a side of the terminal; and in the uplink direction, the transmitting end is a terminating side and the receiving end is a network side, for example, the destination base station.
[0248] In an implementation of this request, if the PDCP layer of the originating base station obtains no data packet flow identifier, the forwarding data packets sent by the originating base station to the destination base station will not include a flow identifier. In this scenario, in the downlink direction, the destination base station can send data packets to the terminal in any of the following ways:
[0249] When forwarding data packets are sent to the destination base station through one or more tunnels established on the basis of a DRB, the destination base station can send the data packets forwarded to the terminal at the first DRB (that is, the reflected DRB) and then, after completing the sending of the forwarded data packets, send, still using the first DRB, another data packet received from the main network through the SDAP layer . It can be understood that the shipping method is applicable both to a scenario where the first mapping relation is the same as the second mapping relation and to a scenario where the first mapping relation is different from the second mapping relation .
[0250] When forwarding data packets are sent to the destination base station through a DRB-based tunnel and a session-based tunnel, the session-based tunnel can be used to transmit the data packet cached in the SDAP layer, and the tunnel established on the basis of a DRB can be used to transmit the data packet stored in
Petition 870190103851, of 10/15/2019, p. 61/96
56/75 cache at the PDCP layer. Specifically, if the second mapping relationship is the same as the first mapping relationship, the destination base station can send the data packets forwarded to the terminal on the first DRB (reflected DRB) and then after completing the sending the forwarded data packets, send, still using the first DRB, another data packet received from the main network through the SDAP layer. If the second mapping relation is different from the first mapping relation, all data packets forwarded in the DRB-based tunnel are sent in the corresponding reflected DRB from the destination base station. The destination base station's SDAP entity can route all forwarded data packets received from the established tunnel based on a session to the new DRB and send the data packets in the new DRB.
[0251] Optionally, the originating base station can allocate a sequence number to a PDCP SDU cached in the PDCP layer, and send to the destination base station as some of the forwarding data packets, the PDCP SDU to which the sequence number is allocated. The details are not described.
[0252] When forwarding data packets are sent to the destination base station through a tunnel established on the basis of a session, the destination base station routes the data packets forwarded to the second DRB based on the second mapping relationship and sends the data packets. The receiving end discards all out-of-service data packets. In addition, the receiving end can notify the destination base station of an initial sequence number of a discarded data packet or a sequence number of a last data packet delivered to the main network. In this scenario, the target base station cannot establish the reflected DRB. Forwarded data packets are all data packets after an identified PDCP layer data packet, and the identified data packet is used to indicate that the transmitting end no longer sends a data packet before the data packet, but the transmitting end repeatedly sends the data packets after the data packet.
[0253] According to the data transmission method provided
Petition 870190103851, of 10/15/2019, p. 62/96
57/75 in this modality of this request, in the direction of downlink, the data packets for forwarding are transmitted through different types of tunnels, and the data packets forwarded are sent to the terminal in transmission ways corresponding to the types of tunnel. In the uplink direction, the terminal sends uplink data packets to the side of the network on different DRBs. In this modality of this request, several flexible ways of transmitting data packets are provided, and a way of transmitting data packets can be selected based on a real state of the network, to avoid the problem: In an automatic switch or double connectivity or another scenario, a data packet is lost or is transmitted repeatedly by the fact that each base station independently configures a mapping relationship between a stream and a DRB. This improves the continuity of the terminal's service and improves the quality of communication.
[0254] FIG. 7 is a structural schematic diagram of an access network device 700, according to an embodiment of this application.
[0255] The access network device 700 is applicable to the communication system shown in FIG. 1. The access network device 700 can perform the operations performed by the first access network device in the mode shown in FIG. 2 or FIG. 5 or the destination base station in the embodiment shown in FIG. 6.
[0256] As shown in FIG. 7, the access network device 700 includes a receiving unit 701 and a processing unit 702.
[0257] Receiving unit 701 is configured to receive forwarded data packets (or a forwarded data packet) from a second access network device.
[0258] Optionally, in an automatic switching scenario, the access network device 700 is a destination base station and the second access network device is a source base station.
[0259] Optionally, in a dual connectivity scenario, the access network device 700 is a secondary base station and the second access network device is a master base station; or the access network device 700 is a master base station and the second
Petition 870190103851, of 10/15/2019, p. 63/96
58/75 access network device is a secondary base station.
[0260] Processing unit 702 is configured to map, to a first DRB, at least one data packet in the forwarded data packets that includes a flow identifier. The first DRB corresponds to a DRB of the second access network device.
[0261] The first DRB and the DRB of the second access network device serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device.
[0262] Optionally, processing unit 702 is additionally configured to map, to the first DRB, a data packet in the forwarded data packets that does not include a flow identifier.
[0263] Optionally, processing unit 702 is additionally configured to map, to a second DRB based on a second mapping relationship, at least one data packet in the forwarded data packets that includes a flow identifier and which is different of the data packet mapped to the first DRB. The second mapping relationship is a mapping relationship between a flow and a DRB on the first access network device.
[0264] The first DRB is a reflected DRB that can maintain a DRB transmission status from the second access network device. The second DRB is a new DRB that is established by the access network device 700 based on the mapping relationship that is between a stream and a DRB and which is configured by the access network device 700, that is, the second connection relationship mapping.
[0265] It can be understood that the first DRB can be used to transmit a data packet that includes a flow identifier or a data packet that does not include a flow identifier, and the second DRB can be used to transmit a data packet data that includes a stream identifier.
[0266] For a detailed description of the first DRB, the second DRB, the first mapping relation and the second mapping relation, consult the related contents in another modality of this request. The details are not described again.
Petition 870190103851, of 10/15/2019, p. 64/96
59/75 [0267] Optionally, processing unit 702 is additionally configured to release the first DRB after sending the data packet in the first DRB is completed. For a detailed description, consult the contents listed in another form of this request. The details are not described again.
[0268] Optionally, in an implementation of this request, the receiving unit 701 is specifically configured to receive data packets forwarded from the second access network device through a tunnel established on the basis of a DRB and a tunnel established with basis of a session. The tunnel established on the basis of a DRB can be used to transmit a PDCP layer data packet that is from the second access network device and to which a sequence number is allocated. The session-based tunnel can be used to transmit a SDAP layer data packet from the second access network device, and / or the session-based tunnel is used to transmit a PDCP layer data packet. which is from the second access network device, which includes a flow identifier, and for which no sequence number is allocated. Then, the processing unit 702 can map, to the first DRB, a data packet received through the tunnel established on the basis of a DRB, and map, to the second DRB, a data packet received through the tunnel established on the basis of in one session.
[0269] Optionally, in an implementation of this request, the receiving unit 701 is specifically configured to receive data packets forwarded from the second access network device through one or more tunnels established based on a DRB. The processing unit 702 can then map the data packet in the received forwarded data packets to the first DRB that does not include a flow identifier, and map the data packet in the data packets to the second DRB. routed that includes a flow identifier.
[0270] Optionally, in an implementation of this request, the receiving unit 701 is specifically configured to receive, from the second access network device through a tunnel established on the basis of a session, the data packet in the data packets
Petition 870190103851, of 10/15/2019, p. 65/96
60/75 routed that includes a flow identifier. Then, processing unit 702 can route, to the first DRB through an SDAP entity, a PDCP layer data packet that is in the forwarded data packets and to which a sequence number is allocated, and route, to the second DRB, a PDCP layer data packet for which no sequence number is allocated or the SDAP layer data packet.
[0271] Optionally, the access network device 700 additionally includes a sending unit 703, configured to send, to a terminal in the first DRB or the first DRB and in the second DRB, downlink data packets that include data packets forwarded. For example, sending unit 703 is configured to: send, to the terminal in the first DRB, the PDCP layer data packet that is in the forwarded data packets and to which a sequence number is allocated, and send, to the terminal in the second DRB, the PDCP layer data packet that is in the forwarded data packets and for which no sequence number is allocated.
[0272] For a detailed description of the receipt of data packets sent through different types of tunnels and a detailed description of the ways of transmitting downlink data corresponding to the different types of tunnels, consult the related contents in another modality of this request. The details are not described again in this report.
[0273] FIG. 8 is a structural schematic diagram of an access network device 800, according to an embodiment of this application.
[0274] The access network device 800 is applicable to the communication system shown in FIG. 1. The access network device 800 can perform the operations performed by the first access network device in the mode shown in FIG. 3 or in FIG. 5 or the destination base station in the embodiment shown in FIG. 6.
[0275] The 800 access network device includes:
a receiving unit 801, configured to receive forwarded data packets (or a forwarded data packet) from a second access network device; and an 802 processing unit, configured to: map, to
Petition 870190103851, of 10/15/2019, p. 66/96
61/75 a first DRB radio data carrier, a data packet in the forwarded data packets that does not include a flow identifier, where the first DRB corresponds to a DRB of the second access network device; and map, to a second DRB based on a second mapping relationship, a data packet in the forwarded data packets that includes a flow identifier, where the second mapping relationship is a mapping relationship between a flow and a DRB in the first access network device.
[0276] The first DRB and the DRB of the second access network device serve a first mapping relationship, and the first mapping relationship is a mapping relationship between a flow and a DRB on the second access network device.
[0277] For a detailed description of the first DRB, the second DRB, the first mapping relation and the second mapping relation, consult the related contents in another modality of this request. The details are not described again.
[0278] Optionally, the processing unit 802 is additionally configured to route, through an SDAP entity to the second DRB, the data packet in the forwarded data packets that includes a flow identifier.
[0279] Optionally, in an implementation of this request, the access network device 800 additionally includes a sending unit 803, configured to: send, to a terminal in the first DRB, a data packet in the forwarded data packets that does not include a flow identifier and to which a sequence number is allocated; and sending, to the terminal in the second DRB, a data packet in the forwarded data packets that includes a flow identifier and for which no sequence number is allocated.
[0280] Optionally, the processing unit 802 is additionally configured to release the first DRB after sending the data packet in the first DRB is completed. For a detailed description, consult the contents listed in another form of this request. The details are not described again.
[0281] Optionally, in an implementation of this request, the
Petition 870190103851, of 10/15/2019, p. 67/96
62/75 receiving unit 801 receives the data packets forwarded through a tunnel between the access network device 800 and the second access network device. In a downlink direction, the tunnel between the first access network device and the second access network device can be established in different ways. For a detailed description of the receipt of data packets forwarded through different types of tunnels and a detailed description of ways of transmitting downlink data corresponding to the different types of tunnels, consult the related contents in another modality of this request. The details are not described again in this report.
[0282] FIG. 9 is a structural schematic diagram of an access network device 900, according to an embodiment of this application.
[0283] The access network device 900 is applicable to the communication system shown in FIG. 1. The access network device 900 can perform the operations performed by the second access network device in any of the modalities shown in FIG. 2 to FIG. 5 or the originating base station in the embodiment shown in FIG. 6.
[0284] The 900 access network device includes:
a processing unit 901, configured to generate a forwarding data packet that includes a flow identifier (or forwarding data packets that includes flow identifiers); and a sending unit 902, configured to send, to a first access network device, the forwarding data packet that includes a flow identifier (or forwarding data packets that include flow identifiers).
[0285] Optionally, in a downlink direction, the forwarding data packet includes at least one type of the following data packets: a PDCP layer data packet that is from the second access network device, to which a number of sequence is allocated, and for which no acknowledgment of receipt is obtained from a terminal; a PDCP layer data packet that is from the second access network device and for which no sequence number is allocated; and a SDAP Service Data Adaptation Protocol layer data packet from
Petition 870190103851, of 10/15/2019, p. 68/96
63/75 second access network device.
[0286] Optionally, in the downlink direction, sending unit 902 can be additionally configured to send, for the first access network device, a data packet for routing that does not include a flow identifier.
[0287] Optionally, in the downlink direction, the sending unit 902 can be configured to send the data packet for forwarding to the first access network device through different types of tunnels. For a detailed description of several tunnels and the transmission of the data package for routing in the various tunnels, consult the contents listed in another modality of this request. The details are not described again in this report.
[0288] Optionally, in an implementation of this request, in the downlink direction, the processing unit can be additionally configured to obtain a flow identifier through a PDCP entity, to add the flow identifier to the data packet for forwarding, and generating the forwarding data packet that includes the stream identifier, and then the first access network device analyzes the forwarded data packet to obtain the stream identifier. For a detailed description of how to generate the data package that includes a flow identifier, consult the related contents in the modality shown in FIG. 5. The details are not described again in this report.
[0289] Optionally, in an uplink direction, the forwarding data packet includes an out-of-service data packet received from the terminal. The access network device 900 can receive the out-of-service data packet using a receiving unit 903. All data packets for forwarding in the uplink direction include flow identifiers. Sending unit 902 can send data packets for forwarding in the uplink direction to the first access network device through a tunnel established on the basis of a DRB. The details are not described in this report.
[0290] FIG. 10 is a structural schematic diagram of an access network device 1000, according to one embodiment of this
Petition 870190103851, of 10/15/2019, p. 69/96
64/75 request.
[0291] The access network device 1000 is applicable to the communication system shown in FIG. 1. The access network device 1000 can perform the operations performed by the first access network device in the mode shown in FIG. 4 or the operations performed by the destination base station in the mode shown in FIG. 6.
[0292] The access network device 1000 includes:
a receiving unit 1001, configured to receive a forwarded data packet (or forwarded data packets) from a second access network device, where the forwarded data packet includes a flow identifier, and the forwarded data packet includes an out-of-service data packet received by the second access network device from a terminal; and a sending unit 1002, configured to send the received forwarded data packet to a primary network device.
[0293] Optionally, the receiving unit 1001 receives the data packet forwarded through a tunnel between the access network device 1000 and the second access network device. The tunnel can be a tunnel that is established between the first access network device and the second access network device based on a DRB. For the tunnel, consult the related descriptions of the tunnel established based on a DRB in another modality of this order. The details are not described again.
[0294] Receiving unit 1001 is additionally configured to receive uplink data packets from the terminal. Uplink data packets include at least one type of the following data packets: a PDCP layer data packet that is unsuccessfully sent by the terminal to the second access network device and to which a sequence number is allocated ; a PDCP layer data packet that is from the terminal and for which no sequence number is allocated; and an SDAP layer data packet from the terminal.
[0295] Optionally, the receiving unit 1001 is specifically configured to receive uplink data packets in a first DRB.
Petition 870190103851, of 10/15/2019, p. 70/96
65/75 [0296] Optionally, the receiving unit 1001 is specifically configured to receive uplink data packets in a second DRB.
[0297] Optionally, the receiving unit 1001 is specifically configured to: receive, in a first DRB, a PDCP layer data packet that is from the terminal and for which a sequence number is allocated in the uplink data packets ; and receiving, in a second DRB, the PDCP layer data packet that is from the terminal and for which no sequence number is allocated in the uplink data packets and / or the terminal SDAP layer data packet in the packets uplink data.
[0298] Optionally, the receiving unit 1001 is specifically configured to: receive, in a first DRB, a PDCP layer data packet from the terminal in the uplink data packets; and receiving, in a second DRB, the SDAP layer data packet from the terminal in the uplink data packets.
[0299] The first DRB is a reflected DRB. The second DRB is a new DRB. For a detailed description of the first DRB and the second DRB, consult the contents listed in another modality of this request. The details are not described again.
[0300] FIG. 11 is a structural schematic diagram of a terminal 1100, according to an embodiment of this application.
[0301] Terminal 1100 is applicable to the communication system shown in FIG. 1. Terminal 1100 can perform operations performed by the terminal in any of the modalities shown in FIG. 2 to FIG. 6.
[0302] Terminal 1100 includes:
a sending unit 1101, configured to send uplink data packets to an access network device, where uplink data packets include flow identifiers; and / or a receiving unit 1102, configured to receive downlink data packets from the access network device, where at least one of the downlink data packets includes a flow identifier.
[0303] Downlink data packets include a
Petition 870190103851, of 10/15/2019, p. 71/96
66/75 forwarded data packet (or forwarded data packets) in a downlink direction. For the specific content of the forwarded data package, see the descriptions listed in another modality of this request. The details are not described again in this report.
[0304] Optionally, sending unit 1101 is specifically configured to send uplink data packets to the access network device in a first DRB.
[0305] Optionally, sending unit 1101 is specifically configured to send uplink data packets to the access network device in a second DRB.
[0306] Optionally, the sending unit 1101 is specifically configured to: send, to the access network device in a first DRB, a PDCP layer data packet that is in the uplink data packets and for which one sequence number is allocated; and sending, to the access network device in a second DRB, a PDCP layer data packet for which no sequence number is allocated in the uplink data packets and / or an SDAP layer data packet in the packets uplink data. The PDCP layer data packet transmitted in the first DRB can be a data packet that includes a stream identifier, or it can be a data packet that does not include a stream identifier.
[0307] Optionally, the sending unit 1101 is specifically configured to: send a PDCP layer data packet in the uplink data packets to the access network device in a first DRB; and sending an SDAP layer data packet in the uplink data packets to the access network device in a second DRB. The PDCP layer data packet includes a data packet to which a sequence number is allocated and a data packet to which no sequence number is allocated.
[0308] Optionally, the receiving unit 1102 is specifically configured to receive downlink data packets from the access network device on the first DRB.
[0309] Optionally, the receiving unit 1102 is specifically configured to receive, from the network device
Petition 870190103851, of 10/15/2019, p. 72/96
67/75 access in the second DRB, a downlink data packet that includes a flow identifier.
[0310] Optionally, the receiving unit 1102 is specifically configured to: receive, from the access network device in the first DRB, a data packet in the downlink data packets that does not include a flow identifier; and receiving, from the access network device in the second DRB, a data packet in the downlink data packets that includes a flow identifier.
[0311] Optionally, the receiving unit 1102 is specifically configured to: receive, from the access network device in the first DRB, a PDCP layer data packet that is in the downlink data packets and for which one sequence number is allocated; and receiving, from the access network device in the second DRB, a PDCP layer data packet that includes a flow identifier and for which no sequence number is allocated in the downlink data packets and a data packet SDAP layer data in downlink data packets.
[0312] The first DRB is a reflected DRB. The second DRB is a new DRB. For a detailed description of the first DRB and the second DRB, consult the contents listed in another modality of this request. The details are not described again.
[0313] The access network device is an access network device that was accessed by the terminal. When the access network device is an access network device accessed by the terminal after an automatic switch or is an access network device that receives data downloaded in a dual connectivity process, the downlink data packets include a data packet forwarded in a downlink direction and another downlink data packet received by the access network device from a main network. For a detailed description, consult the contents listed in another form of this request. The details are not described again.
[0314] FIG. 12 is a structural schematic diagram of an access network device 1200, according to an embodiment of this application.
Petition 870190103851, of 10/15/2019, p. 73/96
68/75 [0315] The access network device 1200 is applicable to the communication system shown in FIG. 1. The access network device 1200 can perform the operations performed by the first access network device in any of the modalities shown in FIG. 2 to FIG. 5 or the destination base station in the embodiment shown in FIG. 6.
[0316] Access network device 1200 includes one or more radio remote units (remote radio unit, RRU) 1201 and one or more base band units (base band unit, BBU) 1202. RRU 1201 can be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transmitter, or the like, and the RRU 1201 can include at least one antenna 12011 and a radio frequency unit 12012. The RRU 1201 is primarily configured to: transmit / receive a signal radio frequency signal, and perform the conversion between the radio frequency signal and a baseband signal, for example, configured to send to the UE information such as the signaling indication described in the previous method modalities. The BBU 1202 is mainly configured to: perform baseband processing, control the access network device, and so on. RRU 1201 and BBU 1202 can be physically arranged together; or they may be physically arranged separately, in other words, the access network device 1200 is a distributed access network device. When the access network device includes a CU and a DU, a function of the RRU can be implemented by the DU, and a function of the BBU can be implemented by the CU; or a function of the RRU and some functions of the BBU are implemented by the DU, and another function of the BBU is implemented by the CU; or some functions of the RRU are implemented by the DU, and another function of the RRU and a function of the BBU are implemented by the CU. This is not limited.
[0317] BBU 1202 is an access network device control center, it can also be referred to as a processing unit, and is mainly configured to complete a baseband processing function, such as channel coding, multiplexing, modulation or dispersion spectrum. For example, the BBU can be configured to control the access network device 1200 to perform the operations performed by the first access network device in any of the modalities shown in FIG. 2 to FIG. 5 or the destination base station in mode
Petition 870190103851, of 10/15/2019, p. 74/96
69/75 shown in FIG. 6.
[0318] For example, BBU 1202 can include one or more plates. A plurality of cards can jointly support a radio access network (e.g., an NR access network) of a single access pattern, or can support radio access networks of different access patterns. The BBU 1202 additionally includes a 12021 memory and a 12022 processor. The 12021 memory is configured to store necessary instructions and necessary data. For example, memory 12021 stores a UE context in the previous embodiment. The processor 12022 is configured to control the access network device 1200 to perform the necessary actions, for example, configured to control the access network device 1200 to perform the actions of the first access network device in any of the modalities shown in FIG. 2 to FIG. 4, or controlling the access network device 1200 to perform the actions of the destination base station in the mode shown in FIG. 5. The 12021 memory and the 12022 processor can serve one or more cards. In other words, a memory and a processor can be arranged separately on each card, or a plurality of cards can share the same memory and processor. In addition, a necessary circuit is additionally arranged on each plate.
[0319] For example, BBU 1202 additionally includes a communication unit 12023. Communication unit 12023 is configured to support the access network device 1200 in communication with a network element such as another access network device or a main network device, for example, supporting the access network device 1200 on receipt of a data packet forwarded from a second access network device. The communication unit 12023 can include a communication interface, for example, a communication interface between the access network device 1200 and the second access network device, or a communication interface between the access network device 1200 and the primary network device.
[0320] FIG. 13 is a structural schematic diagram of an access network device 1300, according to an embodiment of this application.
[0321] The 1300 access network device is applicable to the system
Petition 870190103851, of 10/15/2019, p. 75/96
70/75 of communication shown in FIG. 1. The access network device 1300 can perform the operations performed by the second access network device in any of the modalities shown in FIG. 2 to FIG. 5 or the originating base station in the embodiment shown in FIG. 6.
[0322] The 1300 access network device includes one or more RRUs
1301 and one or more BBUs 1302.
[0323] BBU 1302 can be configured to control the access network device 1300 to perform the operations performed by the second access network device in these modalities shown in FIG. 2 to FIG. 5, or controlling the access network device 1300 to perform the operations performed by the original access network device in the embodiment shown in FIG. 6.
[0324] For example, BBU 1302 can include one or more plates. A plurality of cards for jointly supporting a radio access network (e.g., an NR access network) of a single access pattern, or for supporting radio access networks of different access patterns. The BBU
1302 additionally includes a memory 13021 and a processor 13022. Memory 13021 is configured to store necessary instructions and necessary data. For example, memory 13021 stores a UE context obtained from the first access network device in the previous embodiment. The processor 13022 is configured to control the access network device 1300 to perform necessary actions, for example, configured to control the access network device 1300 to perform the actions of the second access network device in these embodiments shown in FIG. 2 to FIG. 5, or controlling the access network device 1300 to perform the actions of the originating base station in the mode shown in FIG. 6.
[0325] For example, BBU 1302 additionally includes a communication unit 13023. Communication unit 13023 is configured to support the access network device 1300 when communicating with a network element such as another access network device or a main network device, for example, supporting the access network device 1300 in sending a data packet for forwarding to a first access network device. The communication unit 13023 may include a communication interface, for example, a communication interface between the
Petition 870190103851, of 10/15/2019, p. 76/96
71/75 access network 1300 and the first access network device, or a communication interface between the access network device 1300 and the main network device.
[0326] For a detailed description of the functions of the RRU and BBU and a detailed description of the functions of devices, such as the memory and the processor in the BBU, consult the related contents in the modality shown in FIG. 13. The details are not described again in this report.
[0327] FIG. 14 is a structural schematic diagram of a terminal 1400, according to an embodiment of this application.
[0328] Terminal 1400 is applicable to the communication system shown in FIG. 1. The terminal 1400 can perform the operations performed by the terminal in any of the modalities shown in FIG. 2 to FIG. 6.
[0329] To facilitate the description, FIG. 14 shows only the main components of the terminal. As shown in FIG. 14, terminal 1400 includes a processor, a memory, a control circuit, an antenna, and an input / output device. The processor is mainly configured to: process a communication protocol and communication data, control all user equipment, run a software program and process data from the software program, for example, configured to support the 1400 terminal when performing actions of the terminal described in FIG. 2 to FIG. 6. The memory is mainly configured to store the software program and data, for example, to store a terminal context described in the previous modalities. The control circuit is mainly configured to: perform the conversion between a baseband signal and a radio frequency signal and process the radio frequency signal. The control circuit and the antenna can also be referred to together as a transceiver, mainly configured to transmit / receive a radio frequency signal in the form of an electromagnetic wave, for example, it can be configured to: send a data packet uplink to an access network device or receive a downlink data packet from an access network device. For details, see the descriptions listed in the method modalities. The input / output device, such as a touch screen, a display screen or a keyboard, is mainly configured to: receive data entered by a
Petition 870190103851, of 10/15/2019, p. 77/96
72/75 user and send data to the user.
[0330] After the terminal is powered up, the processor can read the software program on the storage unit, interpret and execute instructions from the software program and process the data from the software program. When the processor needs to send wireless data, the processor sends a baseband signal to a radio frequency circuit after performing the baseband processing on the data to be sent. After performing the radio frequency processing on the baseband signal, the radio frequency circuit sends a radio frequency signal in an electromagnetic waveform through the antenna. When data is sent to the terminal, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal and sends the baseband signal to the processor . The processor converts the baseband signal to data and processes the data.
[0331] One skilled in the art can understand that, to facilitate description, FIG. 14 shows only one memory and only one processor. Indeed, the terminal may have a plurality of processors and a plurality of memories. Memory can also be referred to as a storage medium, a storage device or the like. This is not limited in this mode of this application.
[0332] In an optional implementation, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly configured to process the communication protocol and communication data. The central processing unit is mainly configured to: control the entire terminal, run the software program and process the data in the software program. The processor in FIG. 14 integrates functions of the baseband processor and the central processing unit. One skilled in the art can understand that the baseband processor and the central processing unit can alternatively be separate processors, and are interconnected by means of a technology, such as a bus. One skilled in the art can understand that the terminal can include a plurality of baseband processors to adapt to different network standards and the terminal can include a plurality of central processing units
Petition 870190103851, of 10/15/2019, p. 78/96
73/75 to enhance the terminal's processing capacity. The components in the terminal can be connected via several busbars. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. A function of processing the communication protocol and the communication data can be built into the processor or can be stored in the storage unit in the form of a software program. The processor runs the software program to implement a baseband processing function.
[0333] FIG. 15 is a schematic diagram of a communication system 1500, according to an embodiment of this request.
[0334] The communication system 1500 includes a first access network device 1501 and a second access network device 1502.
[0335] The first access network device 1501 can perform the operations performed by the first access network device in any of the modalities shown in FIG. 2 to FIG. 5 or perform the operations performed by the destination base station in the mode shown in FIG. 6. For example, the first access network device may be the access network device in the embodiment shown in FIG. 7, FIG. 8, FIG. 10 or FIG. 12.
[0336] The second access network device 1502 can perform the operations performed by the second access network device in any of the modalities shown in FIG. 2 to FIG. 5 or perform the operations performed by the originating base station in the mode shown in FIG. 6. For example, the second access network device can be the access network device in the embodiment shown in FIG. 9 or FIG. 13.
[0337] The communication system may additionally include a terminal 1503 that communicates separately with the first access network device 1501 and with the second access network device 1502. Terminal 1503 can perform operations performed by the terminal at any among the modalities shown in FIG. 2 to FIG. 6 and can be the terminal in the embodiment shown in FIG. 11 or FIG. 14.
[0338] A technician on the subject can clearly understand that
Petition 870190103851, of 10/15/2019, p. 79/96
74/75 mutual reference can be made between the descriptions of the modalities provided in this application. For example, for a convenient and brief description, for functions and stages of execution of each device and device provided in these modalities of this order, consult the related descriptions in the method modalities of this order. Mutual reference can also be made between the modalities of the method and between the modalities of the device.
[0339] All or some of the preceding modalities can be implemented by software, hardware, firmware or any combination of them. When implemented by software, all or some of the preceding modalities can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When computer program instructions are loaded and executed on a computer, all or some of the procedures or functions, according to the modalities of the present invention, are generated. The computer can be a general purpose computer, a dedicated computer, a computer network, or another programmable device. Computer instructions can be stored on a computer-readable storage medium or they can be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center in a wired manner (for example, a coaxial cable, an optical fiber or a digital subscriber line (DSL)) or wireless (for example, infrared, radio or microwave). Computer-readable storage media can be any usable media accessible to a computer or a data storage device that integrates one or more usable media, for example, a server or a data center. Usable media can be a magnetic media (for example, a floppy disk, a hard drive or a magnetic tape), an optical media (for example, a DVD), a semiconductor media (for example, a solid state disk (SSD) ) or similar.
[0340] In the various modalities provided in this application, it should be understood that the system, device and method disclosed can be
Petition 870190103851, of 10/15/2019, p. 80/96
75/75 implemented in other ways without departing from the scope of this request. For example, the modalities described are merely examples. For example, the module or unit division is merely a logical function division and can be another division during actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some characteristics can be ignored or not realized. Units described as separate parts may or may not be physically separate and parts displayed as units may or may not be physical units, in other words, they may be located in one position, or they may be distributed across a plurality of network units. Some or all of the modules can be selected based on a real requirement to achieve the objectives of the solutions in these modalities. A person skilled in the art can understand and implement the modalities of this request without creative efforts.
[0341] In addition, the system, device, method and schematic diagrams described in different modalities can be combined or integrated with another system, module, technology or method without departing from the scope of this application. In addition, the mutual couplings displayed or discussed or direct couplings or communication connections can be implemented through some interfaces. Indirect couplings or communication connections between devices or units can be implemented in electronic, mechanical or other ways.
[0342] The preceding descriptions are merely specific implementations of this application, but are not intended to limit the scope of protection of this application. Any variation or substitution promptly identified by a technician in the matter within the technical scope disclosed in this order must be within the scope of protection of this order. Therefore, the scope of protection of this claim must be subject to the scope of protection of the claims.

权利要求:
Claims (30)
[1]
1. Data transmission method, CHARACTERIZED by the fact that the method comprises:
establish, through a first access network device, a tunnel based on a radio data carrier (DRB) and a session based tunnel with a second access network device; and receiving, by the first access network device, data packets forwarded from the second access network device through the DRB-based tunnel and the session-based tunnel, in which the DRB-based tunnel is used by the first device access network to receive a Packet Data Convergence Protocol (PDCP) layer data packet from the second access network device; and the session-based tunnel is used by the first access network device to receive a Service Data Adaptation Protocol (SDAP) layer data packet from the second access network device.
[2]
2. Method, according to claim 1, CHARACTERIZED by the fact that the method additionally comprises: mapping, by the first access network device, a PDCP layer data packet in a DRB of the second access network device to a first DRB corresponding to the DRB of the second access network device.
[3]
3. Method, according to claim 2, CHARACTERIZED by the fact that a mapping relationship between a flow and the DRB of the second access network device on the second access network device is the same as a mapping relationship between a flow and the first DRB on the first access network device.
[4]
4. Method according to any one of claims 2 to 3, CHARACTERIZED by the fact that the first DRB and the DRB of the second access network device have the same PDCP sequence number (SN) state and the same hyper-frame number (HFN).
[5]
5. Method, according to claim 3, CHARACTERIZED by the fact that the method additionally comprises:
receive, by the first access network device, the relation of
Petition 870190107509, of 10/23/2019, p. 7/13
2/7 mapping between the flow and the DRB of the second access network device on the second access network device from the second access network device.
[6]
6. Method according to any one of claims 2 to 5, CHARACTERIZED by the fact that the method additionally comprises:
send, by the first access network device, the PDCP layer data packet to a terminal in the first DRB.
[7]
7. Method, according to claim 6, CHARACTERIZED by the fact that the method additionally comprises:
after sending, by the first access network device, the PDCP layer data packet to the terminal in the first DRB, send, by the first access network device to the terminal in the first DRB, a data packet received from a main network.
[8]
8. Data transmission method, CHARACTERIZED by the fact that the method comprises:
establishing, through a second access network device, a tunnel based on a DRB data radio carrier and a session based tunnel with a first access network device; and forwarding, through the second access network device, data packets to the first access network device through the DRB-based tunnel and the session-based tunnel, in which the DRB-based tunnel is used by the second network-based device access to send a Packet Data Convergence Protocol (PDCP) layer data packet to the first access network device, and the session-based tunnel is used by the second access network device to send a data packet SDAP Service Data Adaptation Protocol layer for the first access network device.
[9]
9. Method according to claim 8, CHARACTERIZED by the fact that a first DRB to which a PDCP layer data packet in a DRB of the second access network device is mapped to the first access network device is corresponding to the DRB of the second access network device.
Petition 870190107509, of 10/23/2019, p. 8/13
3/7
[10]
10. Method according to claim 9, CHARACTERIZED by the fact that a mapping relationship between a stream and the DRB of the second access network device on the second access network device is the same as a mapping relationship between a flow and the first DRB on the first access network device.
[11]
11. Method, according to claim 9, CHARACTERIZED by the fact that the first DRB and the DRB of the second access network device have the same sequence number (SN) PDCP state and the same hyper-number state (HFN).
[12]
12. Method, according to claim 10, CHARACTERIZED by the fact that the method additionally comprises:
sending, by the second access network device, the mapping relationship between the flow and the DRB of the second access network device on the second access network device to the first access network device.
[13]
13. Data transmission method, CHARACTERIZED by the fact that the method comprises:
receiving (S301), by a first access network device, data packets from a second access network device;
map (S302), by the first access network device to a first DRB data radio carrier, a data packet in the data packets that does not comprise a flow identifier, where the first DRB corresponds to a DRB of the second device access network; and mapping (S303), by the first access network device to a second DRB based on a second mapping relation, a data packet in the data packets that comprises a flow identifier, where the second mapping relation is a mapping relationship between a stream and a DRB on the first access network device.
[14]
14. Data transmission method, CHARACTERIZED by the fact that the method comprises:
sending (S301), through a second access network device, data packets to a first access network device; wherein a data packet in the data packets that does not comprise a flow identifier is mapped to a first radio data carrier
Petition 870190107509, of 10/23/2019, p. 9/13
4/7
DRB, wherein the first DRB corresponds to a DRB of the second access network device; and a data packet in the data packets comprising a stream identifier is mapped to a second DRB based on a second mapping relation, where the second mapping relation is a mapping relation between a stream and a DRB in the first access network device.
[15]
15. Data transmission method, CHARACTERIZED by the fact that the method comprises:
receiving (S603), by a first access network device, a first mapping relation from a second access network device, where the first mapping relation is a mapping relation that is between a flow and a DRB and that is configured by the second access network device;
receiving (S607), by the first access network device, data packets from the second access network device through a DRB-based tunnel and a session-based tunnel;
send, by the first access network device, a data packet received through the DRB-based tunnel to a terminal on a first DRB, in which a mapping relationship between a flow and the first DRB on the first access network device it is the first mapping relationship;
send, by the first access network device, a data packet received through the session-based tunnel to the terminal in a second DRB, in which a mapping relationship between a flow and the second DRB in the first access network is the second mapping relationship which is configured on the first access network device.
[16]
16. Data transmission method, CHARACTERIZED by the fact that the method comprises:
send (S603), through a second access network device, a first mapping relation to a first access network device, where the first mapping relation is a mapping relation that is between a flow and a DRB and that is configured by the second access network device;
Petition 870190107509, of 10/23/2019, p. 10/13
5/7 send (S607), through the second access network device, data packets to the first access network device through a DRB-based tunnel and a session-based tunnel; where a data packet sent through the DRB-based tunnel is forwarded from the first network device to a terminal on a first DRB, where a mapping relationship between a stream and the first DRB on the first network device access is the first mapping relationship; and a data packet sent through the session-based tunnel is sent from the first network device to the terminal in a second DRB, where a mapping relationship between a flow and the second DRB in the first access network is the second mapping relationship which is configured on the first access network device.
[17]
17. Data transmission method, CHARACTERIZED by the fact that the method comprises:
receiving, by a first access network device, a forwarded data packet from a second access network device, wherein the forwarded data packet comprises a flow identifier, wherein the forwarded data packet comprises a packet out-of-service data received by the second access network device from a terminal.
[18]
18. Data transmission method, CHARACTERIZED by the fact that the method comprises:
generating (S501), by a first access network device, a data packet for routing comprising a flow identifier; and sending (S502), through the first access network device to a second access network device, the forwarding data packet comprising a flow identifier.
[19]
19. Data transmission method, CHARACTERIZED by the fact that the method comprises:
sending, through a terminal, uplink data packets to a first access network device, wherein the uplink data packets comprise flow identifiers; and / or
Petition 870190107509, of 10/23/2019, p. 11/13
6/7 receiving downlink data packets from the terminal from the first access network device, in which at least one of the downlink data packets comprises a flow identifier, and the link data packets descendant comprises a forwarding data packet sent by a second access network device to the first access network device.
[20]
20. Apparatus, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which the at least one processor is configured to execute instructions stored in at least one memory to implement the method as defined in any of the claims 1 to 7, 13, 15 and 17.
[21]
21. Apparatus, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which the at least one processor is configured to execute instructions stored in at least one memory to implement the method as defined in any of the claims 8 to 12, 14, 16 and 18.
[22]
22. Apparatus, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which at least one processor is configured to execute instructions stored in at least one memory to implement the method as defined in claim 19.
[23]
23. Access network device, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which at least one processor is configured to execute instructions stored in at least one memory to implement the method as defined in any of claims 1 to 7, 13, 15 and 17.
[24]
24. Access network device, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which at least one processor is configured to execute instructions stored in at least one memory to implement the method as defined in any of claims 8 to 12, 14, 16 and 18.
[25]
25. Terminal, CHARACTERIZED by the fact that: it comprises at least one processor coupled to at least one memory, in which at least one processor is configured to execute instructions stored in the
Petition 870190107509, of 10/23/2019, p. 12/13
7/7 at least one memory to implement the method as defined in claim 19.
[26]
26. Apparatus, CHARACTERIZED by the fact that the apparatus is configured to perform the method as defined in any of claims 1 to 7, 13, 15 and 17.
[27]
27. Apparatus, CHARACTERIZED by the fact that the apparatus is configured to carry out the method as defined in any of claims 8 to 12, 14, 16 and 18.
[28]
28. Apparatus, CHARACTERIZED by the fact that the apparatus is configured to perform the method as defined in claim 19.
[29]
29. Computer program product, CHARACTERIZED by the fact that the computer program product comprises computer executable instructions, and when computer executable instructions are executed, the method as defined in any of claims 1 to 19 is implemented.
[30]
30. Communication system, CHARACTERIZED by the fact that the communication system comprises an access network device configured to implement the method as defined in any of claims 1 to 7, 13, 15 and 17 and an access network device configured to deploy the method as defined in any of claims 8a 12, 14, 16 and 18.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019019834A2|2020-04-22|data transmission method, device, access network device, terminal, computer program product and communication system

---

US11076398B2|2021-07-27|Methods and apparatuses for configuring radio terminal with numerology of second RAT via first RAT

---

US11076317B2|2021-07-27|Radio access network node, core network node, radio terminal, and methods therefor

---

US11109263B2|2021-08-31|Data transmission method and data transmission apparatus

---

BR112019013617A2|2020-01-07|ACCESS NETWORK NODE VIA RADIO, RADIO TERMINAL, AND METHODS AND MEDIA READABLE BY COMPUTER OF THE SAME

---

BR112020016532A2|2020-12-15|TRANSMISSION METHOD AND NETWORK DEVICE

---

US20200178138A1|2020-06-04|Communication method, base station, terminal device, and system

---

US10944625B2|2021-03-09|Bearer configuration method and related products

---

WO2018170746A1|2018-09-27|Communication method, secondary network node and terminal

---

WO2018228378A1|2018-12-20|Communication method and access network device

---

CN111491370B|2022-02-18|Communication method, network element, system and storage medium

同族专利:

---

公开号 | 公开日

---

CN108924876A|2018-11-30|

---

US20200022213A1|2020-01-16|

---

RU2762681C2|2021-12-22|

---

EP3606149A1|2020-02-05|

---

CN108966282A|2018-12-07|

---

EP3606149B1|2021-06-09|

---

EP3606149A4|2020-04-01|

---

US20210045188A1|2021-02-11|

---

JP6882510B2|2021-06-02|

---

CN110463256A|2019-11-15|

---

RU2019133658A|2021-04-26|

---

EP3941110A1|2022-01-19|

---

RU2019133658A3|2021-04-26|

---

CN108966282B|2019-11-19|

---

US10785825B2|2020-09-22|

---

WO2018171791A1|2018-09-27|

---

JP2020511898A|2020-04-16|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US8830950B2|2007-06-18|2014-09-09|Qualcomm Incorporated|Method and apparatus for PDCP reordering at handoff|

---

EP2213119B1|2007-11-16|2014-01-08|Nokia Solutions and Networks Oy|Mapping quality of service for intersystem handover|

---

US8396037B2|2008-06-23|2013-03-12|Htc Corporation|Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof|

---

CN102368875B|2011-10-18|2017-03-01|电信科学技术研究院|A kind of method setting up connection, system and equipment|

---

US9225449B2|2012-05-11|2015-12-29|Intel Corporation|Performing a handover in a heterogeneous wireless network|

---

CN103945470A|2013-01-18|2014-07-23|华为技术有限公司|Switching method, source communication node and target communication node|

---

JP2018521602A|2015-04-22|2018-08-02|ギーゼッケプラスデフリエント モバイル セキュリティー アメリカ インコーポレイテッドＧｉｅｓｅｃｋｅ＋Ｄｅｖｒｉｅｎｔ Ｍｏｂｉｌｅ Ｓｅｃｕｒｉｔｙ Ａｍｅｒｉｃａ， Ｉｎｃ．|Apparatus, computer-readable medium, and method for modifying a service using advanced data collection functions|

---

WO2015070445A1|2013-11-15|2015-05-21|华为技术有限公司|Method and base station for establishing radio bearers|

---

US9497785B2|2014-06-02|2016-11-15|Intel Corporation|Techniques for exchanging beamforming information for a dual connection to user equipment|

---

US10432291B2|2016-08-09|2019-10-01|Samsung Electronics Co., Ltd.|Method and apparatus for managing user plane operation in wireless communication system|

---

US10834772B2|2016-09-30|2020-11-10|Samsung Electronics Co., Ltd.|Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture|

---

GB201621072D0|2016-12-12|2017-01-25|Samsung Electronics Co Ltd|NR QOS handling|WO2019056325A1|2017-09-22|2019-03-28|Oppo广东移动通信有限公司|Data processing method and related device|

---

US10721648B2|2017-10-12|2020-07-21|Apple Inc.|Device requested protocol data unit session modification in the 5G system|

---

US20190349805A1|2018-05-11|2019-11-14|Mediatek Inc.|User equipments and methods for handling an update on quality of serviceflow to data radio bearermapping|

---

CN111225423A|2018-11-27|2020-06-02|中国移动通信有限公司研究院|Method and device for forwarding data|

---

CN111278065B|2019-01-04|2021-04-02|维沃移动通信有限公司|Data transmission method and network node|

---

CN111436078A|2019-01-15|2020-07-21|华为技术有限公司|Communication method and network device|

---

CN111447650B|2019-01-17|2021-11-19|中国移动通信有限公司研究院|Data forwarding method, equipment and storage medium|

---

CN111586769B|2019-02-15|2021-10-15|华为技术有限公司|Switching method, device and system in wireless communication system|

---

CN111628957B|2019-02-28|2021-10-01|华为技术有限公司|Data transmission method and network equipment|

---

CN111654890A|2019-03-04|2020-09-11|中国移动通信有限公司研究院|Switching method and device and user equipment|

---

CN111726890A|2019-03-21|2020-09-29|中国移动通信有限公司研究院|SDAP entity state switching method, data processing method and communication equipment|

---

CN111866929B|2019-04-30|2022-03-08|华为技术有限公司|Communication method, device and system|

---

CN112399476A|2019-08-15|2021-02-23|华为技术有限公司|Data packet transmission method, terminal equipment and network equipment|

---

CN112584450A|2019-09-30|2021-03-30|大唐移动通信设备有限公司|Anchor point conversion processing method, device and equipment|

---

CN112866311A|2019-11-26|2021-05-28|中兴通讯股份有限公司|Method, system, network equipment and storage medium for simultaneous transmission of FTPuplink and downlink services|

---

CN113498125A|2020-03-20|2021-10-12|华为技术有限公司|Communication method, access network equipment, terminal equipment and core network equipment|

---

WO2021208863A1|2020-04-16|2021-10-21|华为技术有限公司|Data transmission method and communication apparatus|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201710183306.9A|CN108924876A|2017-03-24|2017-03-24|Data transmission method, access network equipment, terminal and communication system|

---

PCT/CN2018/080396|WO2018171791A1|2017-03-24|2018-03-24|Data transmission method, access network device, terminal and communications system|

---